cryptogalaxy VS django-query-profil

Hey All,

I am the original author of the app. This is an update to the project.

Cryptogalaxy [0] is an app which will get any cryptocurrencies ticker and trade data in real time from multiple exchanges and then saves it in multiple storage systems.

Currently supported exchanges : FTX, Coinbase Pro, Binance, Bitfinex, BHEX, Huobi, Gateio, Kucoin, Bitstamp, Bybit, Probit, Gemini, Bitmart, Digifinex, AscendEX, Kraken, Binance US, OKEx, FTX US, HitBTC. Total 20.

Currently supported storages : Terminal Output, MySQL, Elasticsearch, InfluxDB, NATS, ClickHouse, S3. Total 7.

All feedback is welcome.

P.S Created fun twitter bot [1] using the app.

[0] : https://github.com/milkywaybrain/cryptogalaxy

Hey all, update about Cryptogalaxy app.

Cryptogalaxy is an open source app which will get any cryptocurrencies ticker and trade data in real time from multiple exchanges and then saves it in multiple storage systems.

Currently supported exchanges : FTX, Coinbase Pro, Binance, Bitfinex, HBTC, Huobi, Gateio, Kucoin, Bitstamp, Bybit, Probit, Gemini, Bitmart, Digifinex, AscendEX (total 15).

Currently supported storages : Terminal Output, MySQL, Elasticsearch, InfluxDB (total 4).

GitHub link : https://github.com/milkywaybrain/cryptogalaxy

Please use it for your purpose (price dashboard, metrics calculations, algo trading etc anything) and let me know both positive and negative feedback!

P.S I just created a fun twitter bot using the app. Please check it out.

But that's still not backend-specific SQL?

There should be an interface method for this. Why does psycopg call it mogrify?

https://django-debug-toolbar.readthedocs.io/en/latest/panels... :

> debug_toolbar.panels.sql.SQLPanel: SQL queries including time to execute and links to EXPLAIN each query

But debug toolbars mostly don't work with APIs.

https://github.com/django-query-profiler/django-query-profil... :

> Django query profiler - one profiler to rule them all. Shows queries, detects N+1 and gives recommendations on how to resolve them

https://github.com/jazzband/django-silk :

> Silk is a live profiling and inspection tool for the Django framework. Silk intercepts and stores HTTP requests and database queries before presenting them in a user interface for further inspection

I agree that this stuff can definitely be handled better.

https://github.com/django-query-profiler/django-query-profil... has a neat option for detecting likely N+1 queries. I usually use the Django Debug Toolbar for this.

Django's ".only()" method lets you specify just the columns you want to retrieve - with the downside that any additional property access can trigger another SQL query. I thought I'd seen code somewhere that can turn those into errors but I'm failing to dig it up again now.

I've used the assertNumQueries() assertion in tests to guard against future changes that accidentally increase the number of queries being made without me intending that.

The points you raise are valid, but there are various levels of mitigations for them. Always room for improvement though!