Re:How not to structure database-backed web apps: performanc...
by bryanrasmussen on Thursday June 28, 2018 @06:03AM
(#17415513)
True, but on the other hand if the developer gets told they are loading nearly 20,000 objects they should be smart enough to realize something is going to need to be optimized here, and although I don't know how to do it I better find out.
[ Parent
| on HN ]
Re:How not to structure database-backed web apps: performanc...
by crdoconnor on Thursday June 28, 2018 @06:59AM
(#17415797)
That depends upon the context. I've seen developers argue over optimizing ETL processes that weren't in the slightest bit time sensitive, took 25 minutes and were going to be run once.
More often than not I've seen developers fret over performance when it's not actually bothering users. This fetishization of performance seems to be a cultural thing in tech.
Conversely, data integrity, normalization and transactionality are usually given far too little weight.
Re:How not to structure database-backed web apps: performanc...
by TeMPOraL on Thursday June 28, 2018 @08:28AM
(#17416285)
> This fetishization of performance seems to be a cultural thing in tech.
Tell me where you've seen that, because I'd love to move there. From my experience, there is a common fetishization of non-performance. The "premature optimization" adage taken to its extreme - "we can buy more hardware", "developer time > machine time", "who cares about wasting electricity of millions of our users", etc.