3 ms·
this is obviously entirely dependent on the kind of software you're writing. if all you're doing is serving static pages, sure, one server can serve a million
by boucher 19y ago
this is obviously entirely dependent on the kind of software you're writing. if all you're doing is serving static pages, sure, one server can serve a million or more requests a day. but if you have a heavy server side component, like handling large file transfers, or even extensive batch processing, you're going to hit a wall a whole lot sooner.
a simple, effective approach to this problem is to partition your site into services, each of which run independently. then, when it comes time to scale, you can scale each service to its own box and beyond independently, with the added benefit of minimizing downtime to a small sub section of your site.
- DarrenStuart 19y agoI am doing a lot of file creation and file look up stuff on my projects to avoid db hits when servering up static data. I am only using the database for crud stuff and then handing off to create the static pages. I have been impressed with the speed and also how easy it is to flip the storage to Amazon s3 if needed.
- boucher 19y agoYea, systems that can be pretty isolated have a lot to gain from keeping caches on disk instead of going to the database on every request.