-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Document advantage of CCXT-REST over CCXT #17
Comments
Hi, If you are not using nodejs, python or php, then ccxt-rest will allow you to use ccxt even with a different language (i.e. Java, C#, Rust, Go, etc). Also, we have users that’s mainly on NodeJS but are still using CCXT-REST, because it allows them to cluster the integration to the exchanges, instead of just clustering their whole app. Cheers, |
Ok excellent, this would work well because I would like to use the language I already know, newLISP! One final request Franz, would you be able to explain a bit more in detail what you mean when you say ccxt-rest allows you to "cluster the integration to the exchanges, instead of just clustering their whole app"? Thank you very much again for this powerful software! :0) |
how to use CCXT-REST in python? |
@lfzCarlosC same way you use regular REST calls in python |
just touching base but Im upgrading my monolith from a massive nodejs app -> to a nest-js microservice... now-> i can use this rest-api -> to make all my calls to the other endpoint. -> instead of having to write all my own functions I can send requests to a url |
Hi and thanks for CCXT-REST!
I am having trouble understanding what advantage CCXT-REST has over CCXT?
I understood that CCXT already provided the unified API to interact with the exchanges.
Would you be able to explain how one might have advantage using CCXT-REST?
Thank you!
The text was updated successfully, but these errors were encountered: