3 ms·
I 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 cle
by wild_preference 8y ago
I 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.”