3 ms·
I tend to agree but I’ve personally stopped using popular ORMs and instead my own semi-reusable, lighter weight libraries that are closer to the native db drive
by sbr464 8y ago
I tend to agree but I’ve personally stopped using popular ORMs and instead my own semi-reusable, lighter weight libraries that are closer to the native db drivers. I feel like in this longer form writing, having the complete process laid out offers more consistency and understanding of how things work. I also think it’s a no-win situation for an author; use a library/ORM and get an equal amount of negative feedback.
- aikah 8y ago> I tend to agree but I’ve personally stopped using popular ORMs and instead my own semi-reusable, lighter weight libraries that are closer to the native db drivers. One could argue that GraphQL libs like Apollo are ORM by nature. So you're just kind of shuffling things around but you're still using an ORM. ORM is a complicated problem to solve, that light-weighter libraries don't solve, but at the same time ORM can't replace usage of SQL either, as soon as it's time to optimize queries or use dedicated functionalities not covered by an ORM library. Fortunately, some databases are now better at returning complex multidimensional datas using object aggregation functions in order to avoid N+1 queries, unfortunately, most do that in a proprietary way and the standard totally lacks on that aspect.
- _hardwaregeek 8y agoYeah, the author handled it nicely, and overall this is a fantastic tutorial. I'm wondering more in terms of the Node ecosystem as a whole.