Hi Patrice, Sarah, isn't even mentioning ACID, that's all me. I'm glad they now have it for single documents. Her post is more on schemeless DB versus traditional DB's and things like transactions., joining, and all the things that make a DB tick. Thing is, the problem is the lack of scheme, and the need to replicate stuff. If your DB grows in complexity, you need to denormalize the data to be able to cope with the changing requirements. Denormalizing and nonrelational databases, don't go well together. You can use something as Mongo as a cache in front of a relational DB, No problem there. Some workloads are suited for a noSQL solution, but as practice learned us, that's not always the case. I still stand by my words. That doesn't mean NoSQL databases are unfit for all goals but preferring them as the main solution for everything still might be a sigh of an inexperienced team.
Regards Sander -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to angular+unsubscr...@googlegroups.com. To post to this group, send email to angular@googlegroups.com. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
