3 ms·
Those writeups are helpful in the same way that watching NASCAR prepares you for a driving test. There is a huge gap between scaling your typical web app and r
by byoung2 15y ago
Those writeups are helpful in the same way that watching NASCAR prepares you for a driving test. There is a huge gap between scaling your typical web app and running Amazon, Twitter, or Facebook. Between the millions of small web apps out there and the few hundred that warrant setups written about on highscalability, there are sensible steps you can take toward scaling that involve sensible architecture choices, database structure and indexing, layers of caching, load balancing and failover, etc. This is where the low hanging fruit is, and I think this is a good place to start.
- Joakal 15y agoI disagree. I've found it useful for a list of buzzwords that I can later look up as keywords. Plus, the organisations using it proves that there tends to be merit. You also provided keywords too though. Also, I saw some posts that talk about bottlenecks as they scale up. You can't really get this from looking at software documentation unless they really emphasise it.
- byoung2 15y agoYou've proved my point. Watch NASCAR and you'll see there are certain challenges that will only present themselves when you're driving 200+ mph. These can be useful to keep in mind as you are learning how to drive for the first time, but there are more immediate issues to focus on, like how to hold the steering wheel properly, shift gears, and use the gas/brake. It won't help much in the practical sense to study advanced drafting techniques at that point if you can't even pull out of the driveway, but if it helps motivate you over the long term, then that's fine. Similarly, I don't think it is beneficial to talk about switching to MongoDB and node.js because you think PHP/MySQL is slow when you haven't even learned how to add indexes and caching.