If you had a solution for an online store based on a relational DBMS SQL Server, what would be the reason, if any, to move to NoSQL storage? Does it make sense to migrate data warehouses that rely heavily on relationships with NoSQL? If you start from scratch, you would choose a NoSQL solution over the relational for the online store project, after some time again receiving a bunch of tables, such as articles, classifications, tax registers, price lists, etc., As well as the relationship between them
What support, for example, in .NET (4.0) to support MongoDB or MongoDB for .NET 4.0? Can I count on rich code generation tools like EF wizards, L2SQL wizards, etc. For MongoDB?
Since, as I already read, NoSQL is mainly suitable for storing documents, simpler object models.
Your answer to this question will help me make the right decisions on infrastructure design.
UPDATE: if I were developing my solution around ASP.NET MVC and relying heavily on Model classes, would it be the easiest way to choose DB4o to simply serialize and deserialize my objects in the data store and from the data store?
source
share