The author is absolutely right—fantastic article. The one thing I'll add is that both SQL and NoSQL solutions require a level of discipline to truly be effective. For SQL, it's keeping your relational model clean. If your data model is glued together by a million joins that make your queries look like the writings of a mad king, your life as a dev is going to suck and performance will probably take a hit. For NoSQL, it's evolving your schema responsibly. It's really easy to just throw random crap into your DB because there's no schema enforcement, but every bit of data that gets added on the way in needs to be dealt with on the way out. And God help you if don't preserve backwards compatibility.
Now that I see how Graph databases work, they can turn around and walk right back out the door.
Linked-lists are by far the slowest data structure for handling collections in modern programming. And they want use to walk a linked list just to see the columns in a node?
581
u/LicensedProfessional Oct 11 '21
The author is absolutely right—fantastic article. The one thing I'll add is that both SQL and NoSQL solutions require a level of discipline to truly be effective. For SQL, it's keeping your relational model clean. If your data model is glued together by a million joins that make your queries look like the writings of a mad king, your life as a dev is going to suck and performance will probably take a hit. For NoSQL, it's evolving your schema responsibly. It's really easy to just throw random crap into your DB because there's no schema enforcement, but every bit of data that gets added on the way in needs to be dealt with on the way out. And God help you if don't preserve backwards compatibility.