Comments by "Edward Cullen" (@edwardcullen1739) on "DONT USE AN ORM | Prime Reacts" video.

  1. Concur. "Micro ORM"s, like Dapper, that automate the Object-ification of query results are where the usefulness of ORMs start and finish.
    23
  2. "Makes refactoring easier." Not when you have real-world amounts of data. For toy databases, sure, but "refactoring" database tables for serious applications is no joke and ORMs are more of a hindrance than a help. Something like Dapper is good, for eliminating the tedium of Object-ifying query results, but direct table access and ORM-generated queries are simply the route to a long-term maintenance nightmare.
    6
  3. ​ @siniarskimar  LOL, yeah, same. Because that's how most people react when they have to use it. 😂
    3
  4. My experience is that most ORMs are dumb as a brick and about as useful when it comes to real-world software. I have direct knowledge of one well-known piece of software that had to engage in a complete rewite of their DB layer because the ORM became a performance bottleneck. This is worse than it sounds, because you have to mix the ORM code with hand-written stuff, so it becomes an absolute nightmare to maintain. Fun, if you're deeply into SQL/are a complete masochist. But for normal people, not so much...
    2
  5. You only hate stored procedures, until you're working for a large company with 30+ years of database evolution where many different teams are doing raw table access... And it is your job to modify said tables. I worked with an experienced dev who worked for 2 massive UK retailers - his wisdom on this was undeniable and has stuck with me. He absolutely required all DB access via stored proc. As to business logic in DB layer, this is a guideline, not a rule. One that you should try really, really hard to stick to, but if the alternative is to slurp gigs of data across the network to get megabytes of useful results...
    1
  6. ​ @hannessteffenhagen61  This.
    1