In 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.”
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.”