3 ms·
This is a really tough problem to solve. I know Alibaba and WePay both have made solutions to try and handle it at scale https://github.com/seata/seata https:/
by dkhenry 6y ago
This is a really tough problem to solve. I know Alibaba and WePay both have made solutions to try and handle it at scale
https://github.com/seata/seata https://github.com/seata/seata
https://wecode.wepay.com/posts/waltz-a-distributed-write-ahead-log https://wecode.wepay.com/posts/waltz-a-distributed-write-ahe...
At the end of the day I don't think anyone should be coding distributed transactions into their app's. If you need use a solution that abstracts them for you. Eventually we will get one into Vitess ( https://vitess.io https://vitess.io ) when we have figured out something general purpose enough to work for lots of workloads
- mindcrime 6y agoJBoss Narayana provides a useful implementation of the Saga Pattern that makes it fairly easy to plug that pattern into microservices interactions.
- ratneshsingh35 6y agoin one of the situation, we had a similar problem of scaling and consistency not going hand in hand, at that time batch process solves Lot of our problems.