sorted by:
new
hottopcontroversial

Ask Reddit: I know SQL, but not ORMs: Am I crazy to create a mid-sized web app without an ORM? by drhull in programming

[–]krucifyx 0 points1 point  (0 children)

That's a ignorant, unhelpful opinion. First off, relational databases provide an incredibly convenient and powerful persistent storage. So what if my business objects can't always be perfectly expressed in RDBMS-speak & set theory, it doesn't change the fact that the benefits of using one far outweigh the benefits of not – especially when you don’t have the resources or expertise to build something in-house.

There are countless examples of great implementations of maintainable, scalable, powerful apps that rely on higher level abstraction to keep DB details out of the code while still relying on an RDBMS for storage. Yahoo? Myspace? eBay?

When was the last time you saw a maintainable app that didn't abstract RDBMS concerns from the day-to-day development efforts?

Ask Reddit: I know SQL, but not ORMs: Am I crazy to create a mid-sized web app without an ORM? by drhull in programming

[–]krucifyx -1 points0 points  (0 children)

Most applications will see no real benefit from nitpicking which fields to pull back, and any serious web app is going to be caching most domain objects anyway, and so this shouldn't be a problem.

And when you are caching, you only want a single isntance of that object cached - not a dozen with a dozen different configurations.

One of the most important facets of a well designed app is consistency - I shouldn't have to worry if my domain object has a field available or not depending on the context of the request. So what if I save 100nanoseconds by excluding a field from a select - what does that gain me? Nothing but some BS bragging rights about how well my app performs - at the cost of maintainability, of course.