Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

NoSQL will bring it's own set of issues right? Too flexible of a system with no built in Validations would mean that they need to be handled somewhere else. If we take the example in the post, refund should not precede awaiting payment, If a new status gets added, it becomes easy to know where the migrations have to be run and in NoSQL, either we write something custom or handle it each time the document is called.



not sure what you are onto but SQL is just old and useless, glad i never had to learn it


Surely that logic should not sit in persistance layer though?


I mean, you shouldn't be throwing shit at the DB and seeing what sticks, but why not have the absolute source of truth also be the validator? CHECK constraints are fairly cheap.


They also derisk deploys of application code. If you deploy a bug that doesn't uphold your constraints, you get failures rather than corruption.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: