3 ms·
Just to clarify, by "stupid amount of different components" I meant more that a typical visit to website can involve tons of different, standalone components: D
by Osmose 13y ago
Just to clarify, by "stupid amount of different components" I meant more that a typical visit to website can involve tons of different, standalone components: Database, application server, cache, load balancer, CDN, browser, etc.
Your comment seems more focused on libraries, frameworks, and languages, but I may be reading it wrong.
- Retric 13y agoAs a counter example. This website does not use a CDN, cache, load balancer, or from what I understand even a Database yet it's ranked ~1,515 in the US by alexa. Which is probably why it's also fairly low maintenance.
- Osmose 13y agoThat's a fair point, although there's a few caveats (HN uses CloudFlare I think, and replace "database" with "filesystem" and it's still another component to deal with). My counter-argument would be that HN is able to avoid a lot of the complexity due to the nature of what it does. Oftentimes the value in adding a new component is maintainability vs doing it the simple way, which is one of the tradeoffs I was referring to earlier. Imagine scaling Google Analytics.