I am building a data aggregation environment on Kubernetes. In my use case I am aggregating blockchain history one block at a time incrementally. To speed things up, I am deploying multiple instances of my data aggreation app. I persist the latest aggregated block number in order to avoid two instances fetching the same block. This is not sufficient as I am seeing duplicates.

What are strategies that I can implement that will ideally remove the possibility of two instances fetching the same block?

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.