rustyrazorblade

It sounds like you're conflating strong consistency with ACID transactions. The strong consistency guarantee with QUORUM writes with Cassandra is only if the write is acknowledged as successful. If you write something successfully, you'll be able to read it. When a write fails the end state is undefined.

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.

Hi. Presenter here. Honestly the goal wasn't to sound fancy. If you're going to work in the GraphDB world, you're going to come across this terminology.

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.

You're right, there's some inconsistencies in the code vs the slides. Must have missed that. I'll fix that going forward.

Nope, quite the opposite (at least the part about me). I'm the guy that loves & thrives on talking to people.

On the contrary, I love what I do and the company I work for. This has nothing to do with my employer.