(2010-08-31) Indelicato Mixing Sql And Nosql

Max Indelicato thinks that mixing SQL and No[[SQL]] makes the most sense.

*My[[SQL]] does transactions well thanks to Inno D B. It’s ACID compliant and has full transactional support.

MongoDb, on the other hand, has neither ACID compliance nor full transactional support. In fact, it has no transactional support.

This is a no-brainer. My[[SQL]] is the more appropriate tool for the job of payment transactions. And that works out fine for us, because this is a Shared-Nothing architecture – payment transactions have little to nothing to do directly with the recording of individual unique visitors or pageviews... I would take this even further and say that all user, account, and payment data in general should be housed within our My[[SQL]] database. Can the other stuff be done in Mongo D B? Yes, it can, but there are more logical relations between those three groups of data than there are between them and unique visitors/pageviews. Keeping related data together is what My[[SQL]] is good at, so let’s take advantage of that here.*

Then he puts all the details data (he's using an Analytics system for this scenario) into MongoDb.

Note that Theo Schlossnagle has said that he wouldn't trust My[[SQL]] for payment transactions, preferring Postgre[[SQL]] or others. But that was almost 2 years ago, so it's possible he's changed his mind... 2008-10-08-SchlossnagleCtoClub