I think you’re throwing the baby out with the bath water here a bit. I agree that stored-price are rarely, if ever the solution. I do however think that havin

I think you’re throwing the baby out with the bath water here a bit. I agree that stored-price are rarely, if ever the solution. I do however think that having something that enforces certain constraints across all your data, and forces you to handle schema evolutions reasonably over time is really powerful. Database implementations are (mostly) full of hard-fought correctness decisions, and I don’t think most devs are in a position to “whip out” an implementation that cares for a number of these on-demand. We had the whole NoSQL thing, we saw what when we threw most of this stuff away. Is sql good enough? For many problems yeah. Is it _really_ good enough? Nah probably not, we could do a lot better, but I think a better design looks more like a better sql-like language and less like a full programming language.