General question about bitcoinexchangefh

[gavincyi]

Yes correct the whole project was redesigned and the objective is to improve the performance and prepare for the future features, e.g. various of handlers e.g. kafka and redis. The redesign also enhanced the features that users requested before

1. Configuration of number of price depth
2. Table rotation
3. Support of exchanges

The reason I rely on ccxt and cryptofeed is to leverage the open source resources on market access. Ccxt may have little overhead on the feed handler while cryptofeed did a pretty good job on the latency. With both, the users can access to more than 130 exchanges in REST API and a few of the most liquid exchanges in websocket API. For me it's a win-win situation that I can reserve more time on designing the feed handler in high level while users can have a good exchange coverage.

Finally a big change from the previous version is that I dropped the multithreading but introduced multiprocessing for performance. This is very important to me as I can ensure the I/O blocking does not cross impact each component, e.g. exchange / handler.

Open for further ideas, comments and even critic.