My company is building a realtime analytics service for security. You have a lot of reads that can often be answered with stale data (thanks to our data modeling, which provides ACID 2.0 semantics).
I think a lot of applications could probably benefit from this if they were built with a data model in mind that leverages it properly. But if you 1:1 migrate your code that relies on ACID transactions over to something with Strong Eventual Consistency... yeah, that's gonna be a bad time.
I think a lot of applications could probably benefit from this if they were built with a data model in mind that leverages it properly. But if you 1:1 migrate your code that relies on ACID transactions over to something with Strong Eventual Consistency... yeah, that's gonna be a bad time.