I mostly agree with your sentiment, that relational databases were created and optimized for a data first approach and SQL was made specifically to interact with it. Whereas ORMs attempt to mold it into a more familiar object oriented approach which can be finicky sometimes.
I think that's where NoSQL came in as a more lenient and object oriented approach to storing data.
That being said, I would recommend new developers to learn SQL and database normalization before using an ORM.
I wrote an article as well about designing a database from a data first perspective and I can understand why people would rather do it a more familiar way with ORM.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey Tyler great write-up!
I mostly agree with your sentiment, that relational databases were created and optimized for a data first approach and SQL was made specifically to interact with it. Whereas ORMs attempt to mold it into a more familiar object oriented approach which can be finicky sometimes.
I think that's where NoSQL came in as a more lenient and object oriented approach to storing data.
That being said, I would recommend new developers to learn SQL and database normalization before using an ORM.
Thank you! I wish there were more of you.
Haha I'm still a beginner at SQL but thanks!
I wrote an article as well about designing a database from a data first perspective and I can understand why people would rather do it a more familiar way with ORM.