You have to think about partitioning up front. In a sense, this is a prerequisite for our concurrency. So you're right. What I meant was, inside of a stored pr

You have to think about partitioning up front. In a sense, this is a prerequisite for our concurrency. So you're right. What I meant was, inside of a stored procedure itself, you never have to think about concurrent access to the data you are modifing during the lifetime of the procedure. You own it. Period. I wouldn't ever try to make the argument that this functionality is "free" and that VoltDB is a system without tradeoffs. It just seemed particularly relavent when the original article was making claims that serializable transaction semantics in SQL-RDBMSs were rare due to performance issues. I didn't mention NoSQL or Key-Value stores anywhere in my original comment.