4 ms·
NoSQL is an excellent technology for rapid R&D, but once a domain “settles”, data should be modeled and data stores should be switched to relational or graph ba
by ChicagoDave 8y ago
NoSQL is an excellent technology for rapid R&D, but once a domain “settles”, data should be modeled and data stores should be switched to relational or graph backends.
If a system already has a well-defined domain, NoSQL adds little value.
Of course you could leverage AWS DynamoDB and reduce cost, but you still have downstream implications for things like reporting, which requires a known schema with relational paradigms.
- wild_preference 8y agoI don’t see how NoSQL could be better for rapid dev when something like Postgres can migrate its schema and data at once while enforcing constraints. That’s clearly better precisely when your schema is changing.
- ChicagoDave 8y agoIn R&D scenarios, NoSQL wins hands down because devs are jamming schema changes hourly. That level of frequency in a relational model is a massive drag on time and it’s wasted. If it’s a redevelopment of a well-known domain, depending on reporting requirements, I’d slightly side with relational. But AWS DynamoDB can be a huge cost savings, so as any good architect will say, “It depends.”
- gwbas1c 8y agoI used to tell people that MongoDB was the "visual basic of databases." Easy and useful for very simple applications.