I think the problem here is NoSQL, for a RDBMS wouldn’t be a problem with data integrity, that’s why I’d prefer it over NoSQL, while it can be easier to start p

I think the problem here is NoSQL, for a RDBMS wouldn’t be a problem with data integrity, that’s why I’d prefer it over NoSQL, while it can be easier to start prototyping without a defined structure, I’m more confortable doing with it. Last year I tried a lot of those new document oriented databases and for me, they are awful, you can’t be sure what’s in each record, so I need to be more careful with my application logic and not to mess up, while you can easily define your structure and constraints with a RDBMS and be confident that your data is always correct, also, when adding new fields it’s a nightmare without migrations. This year I started thinking that we might need a database that lets us write proper stored procedures and that it feels like programming (I mean PL/SQL feels pretty hard and it seems that not so many devs are using it), for example what I wanted was to create a trigger when a user buys something, subtract the quantity from the inventory and create a new entry in notifications and orders, that way my app just needs to check if there’s unsent notifications and show the user their orders without that logic being in my app, and it does feels easy to just edit those procedures with migrations.