The definition of strong consistency does not require a rollback, nor does it define the behavior of the system during a write failure. Strong consistency makes no assertions regarding atomicity (all or nothing) or isolation.
171 karma · joined January 3, 2013
The definition of strong consistency does not require a rollback, nor does it define the behavior of the system during a write failure. Strong consistency makes no assertions regarding atomicity (all or nothing) or isolation.
If your concern around my intro is the complexity described of the relational world, well, that's kind of the point. Anyone with at least a few years experience in the RDBMS world has probably come across a project that's spiraled completely out of control with a outrageous number of many to many relationships that are almost impossible to work with. The role of the DBA just to manage your queries and tables is a reflection of that difficulty.
GUN looks like a cool project. Good intro, & thanks for the feedback.
https://github.com/StartTheShift/thunderdome
There's a few caveats that come with working with distributed databases, so it's important to know what you're getting into. Neo4j might be easier out of the box (since more people are using it), but if you want a robust solution that'll work for 50 or 50,000 users, Titan feels like the way to go.