Sibbo@sopuli.xyz to Programmer Humor@lemmy.ml · 5 months agoPopular Programming Book "Clean Code" is being rewrittensopuli.xyzimagemessage-square111fedilinkarrow-up1624arrow-down111file-text
arrow-up1613arrow-down1imagePopular Programming Book "Clean Code" is being rewrittensopuli.xyzSibbo@sopuli.xyz to Programmer Humor@lemmy.ml · 5 months agomessage-square111fedilinkfile-text
minus-squareTja@programming.devlinkfedilinkarrow-up2·5 months agoIt’s literally what an orm does, and it’s good enough for 80% of apps out there. Using it for the wrong purpose is what’s silly.
minus-squareevatronic@lemm.eelinkfedilinkEnglisharrow-up1·edit-25 months agoI see. It seems like you may be one of the people that try to coerce relational models into nosql stores like Dynamo. Or course it’s possible. They even trick you into thinking it’s a good pattern by naming things “tables”. But if you’re using Dynamo to its fullest an ORM is not going to be able to replicate that into a relational store without some fundamental changes.
minus-squareTja@programming.devlinkfedilinkarrow-up1·5 months agoHence 80%. Most apps out there are a CRUD with a thin layer of logic. If you are in the 20% that needs real performance, an ORM is not gonna cut it, no matter what DB you have.
It’s literally what an orm does, and it’s good enough for 80% of apps out there. Using it for the wrong purpose is what’s silly.
I see. It seems like you may be one of the people that try to coerce relational models into nosql stores like Dynamo.
Or course it’s possible. They even trick you into thinking it’s a good pattern by naming things “tables”.
But if you’re using Dynamo to its fullest an ORM is not going to be able to replicate that into a relational store without some fundamental changes.
Hence 80%.
Most apps out there are a CRUD with a thin layer of logic.
If you are in the 20% that needs real performance, an ORM is not gonna cut it, no matter what DB you have.