Update on web scalable EOS History API

eostribe(55)
Published in
#eos
Words
136
Reading
1 min
Listen
Play
8y

ElasticSearch-History.png

EOS Tribe have implemented an additional History API endpoint for /v2/history/get_key_accounts

Below is our logical diagram for ElasticSearch cluster supporting currently 3 ES nodes with data shared across them:

ElasticSearchAPI.png

All History API source code for Elasticsearch is available at our public repo:
https://github.com/EOSTribe/ESHistoryAPI

Special thanks to EOSLaoMao for developing Elasticsearch plugin used:
https://github.com/EOSLaoMao/elasticsearch_plugin

As of a time of this article on December 23, 2018 at 7:30am Los Angeles time our Elasticsearch cluster is synced up to 27931400 blocks and all historical data is available up to this block.

We will make a separate announcement once our Elasticsearch cluster is fully synced with the Blockchain.

Meanwhile we are working on remaining History endpoint.

All matching /v1/history/* endpoints are now redirected to available /v2/history/* endpoints and both available at https://api.eostribe.io/v2/history/*

EOS Tribe updated Infrastructure diagram:
EOS Tribe Infrastructure V3.png


Website | Medium | Github | Telegram | FB | Twitter | Discord