4 ms·
If you're using JS or Python, the SQL call just returns an array of objects/records. No muss. No fuss. If you're using something like Sqlx in Rust, the SQL is
by ttfkam 3y ago
If you're using JS or Python, the SQL call just returns an array of objects/records. No muss. No fuss.
If you're using something like Sqlx in Rust, the SQL is not just checked for validity, it seamlessly assigns the result set to the exact type you define for that use case.
ORMs make basic CRUD fast and easy while making everything else massively more complex. If all you ever need is CRUD, I guess that's alright. Many of us work with projects that far exceed it though. And for that, you need to know SQL and not just some half-baked SQL punch through the ORM deigns to afford to you.
- swader999 3y agoYou can use cqrs to just build simple reporting views that orms get and set and for your real concurrency boundaries build aggregates that hydrate their state from all the events that have happened to it. Handles complexity to the nines and gets your reports and screens wicked fast at any scale you can imagine. You won't need to join much or optimize queries. Maybe figure out a few non obvious indexes.
- ttfkam 3y ago> And for that, you need to know SQL and not just some half-baked SQL punch through the ORM deigns to afford to you. That and read replicas. Relying on the ORM will not save you, but knowledge of SQL (specifically materialized views) will.