EOS Tribe have built Elasticsearch cluster for Worbli blockchain to provide History API with additional options like date ranges previously implemented for EOS.
See our earlier related post: https://steemit.com/eos/@eostribe/eos-history-api-with-date-ranges
curl -d '{"id": "c55980dfb41e5f2072ba370feb23804d896e59465179b078fe82c68621f60418"}' -X POST https://api.worbli.eostribe.io/v1/history/get_transaction
curl -d '{"account_name":"eosio", "last_days": 7}' -X POST https://api.worbli.eostribe.io/v1/history/get_actions
curl -d '{"account_name":"eosio", "from_date": 1541545834, "to_date": 1541545837}' -X POST https://api.worbli.eostribe.io/v1/history/get_actions
We are working on providing additional API endpoints.
While Worbli have not yet reached scalability issues with native History API, we would like to be ready and have a solution when those issues arise. Additionally API based on Elasticsearch can support higher number of concurrent requests.
You can see more info on hardware specs and Data Center we use in our original post:
https://steemit.com/eos/@eostribe/eos-tribe-infrastructure-upgrade
Website | Medium | Github | Telegram | SteemIt | Twitter | Discord