Keep CALM and CRDT on [pdf](vldb.org)
vldb.org
Keep CALM and CRDT on [pdf]
https://www.vldb.org/pvldb/vol16/p856-power.pdf
8 comments
Author here. Happy to answer any questions. - Conor
There's a need because WAL/OTs aren't the most approachable.
It's important to communicate and assure ACID and CAP properties. It'd be nice to have an "ORM" data layer that's say an extension of GraphQL that can specify what sort of guarantees the app wants.
It's important to communicate and assure ACID and CAP properties. It'd be nice to have an "ORM" data layer that's say an extension of GraphQL that can specify what sort of guarantees the app wants.
I've been using databases that offer strong consistencies, and only recently came across the concept of weak consistency, or eventual consistency. But there seems to be too many varieties of weak consistencies and it's so hard to figure out the nuances and know whether my app is safe under a certain consistency model. This line of research seems to help with that, but oftentimes applications interact with DB in different patterns, and I am not sure if you can get these all covered..
jepsen.io has a neat diagram of various consistency models - http://jepsen.io/consistency
also, you can find talks of Martin Kleppmann on youtube about consistency guarantees, e. g., https://www.youtube.com/watch?v=5ZjhNTM8XU8
also, you can find talks of Martin Kleppmann on youtube about consistency guarantees, e. g., https://www.youtube.com/watch?v=5ZjhNTM8XU8
Do they have a Github repo related to this effort?