> Web apps very often require some persistent application state. Setting up a database involves numerous configuration steps and the subsequent integration of a

> Web apps very often require some persistent application state. Setting up a database involves numerous configuration steps and the subsequent integration of an ORM or other systems. So this is a NoSQL argument. > Atomic transactions: a database that provides atomic operations to ensure data integrity and enable complex application logic Ok, so let's see if they mention "ACID". Nope. They do mention atomicity and durability, but they don't mention consistency and isolation. So this is about NoSQL and NoACID, but it's not really stated this way. K/V stores are great for many things. And not having a query language is great!! right up until you need one, then you get to be sad (I should know since I've had to write a query engine due to use of a K/V store). [No]ACID is where NoSQL gets interesting, IMO. But NoACID doesn't mean you can't have a query language. Anyways, if you're going to implement yet another K/V store you really should justify it in relation to other K/V stores that exist, not as "using RDBMSes is ETOOHARD".