Hot Cross Infrastructure Update

This is an improvement to back-end services to overcome issues or/and add improvements:

Bulk data cannot be read directly from the blockchain so data like total participants in a pool would never be possible with the old infrastructure;
Several issues in the dapp itself due to RPC endpoints failing on a regular basis (nothing we could do about);
Expected improvement in the load times because of lower dependency on the external unstable RPC nodes;
Better in-dapp caching using local storage;
Issues with a centralized price aggregator i.e. CoinGecko;
we now have a separate price feed service that runs independently and purely relies on DEXes
First full scale utilization of
Cross Index
we’ve been building during the last month (more on this soon);
Other features will be possible such as total claimed that can work across devices; because total claimed falls into the category of
bulk requests
, the current implementation has some limitations such as the value will be zeroed after browser cache is cleared and also it cannot work across devices;
Other tech-related changes that are used in not highly-scaled systems. We utilize Kafka and Redis to log all events that happen on the blockchain and then create various views of that data using a much faster and reliable technology. We also utilize neo4j to store the data in a graph database which allows us to make
rich queries
;
We also decided to
switch our tech stack
from purely JavaScript based into a more mixed one where Rust becomes our language of choice for back-end services;
Finally all those changes become the basis for all our future products.

Thank you for using the Hot Cross product suite and do continue giving us your feedback as it comes to mind.