i doing project requires frequent database access, insertions , deletions. should go raw sql commands or should prefer go orm technique? project can work fine without objects , using sql commands? affect scalability in general?
edit: project 1 of types user isn't provided content, user generates content, , project online. so, amount of content depends upon number of users, , if project has 50000 users, , additionally every user can create content or read content, apt approach?
i'd it's better try achieve objective in simple way possible. if using orm has no real added advantage, , application simple, not use orm. if application processing large sets of data, , there no business logic, not use orm.
that doesn't mean shouldn't design application property though, again: if using orm doesn't give benefit, why should use ?
Comments
Post a Comment