I've long felt that NoSQL does not jive with a certain type of mindset many computer professionals have. There is this sterile perfect world mindset many compu

I've long felt that NoSQL does not jive with a certain type of mindset many computer professionals have. There is this sterile perfect world mindset many computer professionals idealize. Transactions and traditional RDBMSes make this sort of person really happy. They love to see everything always working out. That when it doesn't, everything is taken care of for them, etc. I do not know if you're this type of person, but your comment sounds like the type of sentiment that type often expresses when they see NoSQL in real world apps This is not a work around of a messy system. This is adding more consistency on a system which is designed to be fast a scalable more than consistant. Fast and scalable is more important with something like netflix. It's going to bother someone a hell of a lot more if they get fits and starts with their streaming, if it takes forever to get a pageview, etc, than if something occasionally get's misordered in a queue. If they went with a system that demanded consistency over speed/scalability, then what they MIGHT get is a backend database that never went out of sync, but the UI of the website would show that queue items had moved, but the write conflicts would cause the transaction caused by the UI to unroll, and thus the user would still experience inconsistency. Or the website could wait for a confirmation for every step and offer a horrendously slow user experience during peak times. I think this sort of NoSql data garden with automated gardeners running through all the time will be a fairly typical path from now on for many types of systems. I think financial apps may even adopt it eventually!