3 ms·
Scalability isn't a magic pixie dust you find in some boxes of cereals and not others. Scalability is extremely application specific. As your application grows
by swombat 18y ago
Scalability isn't a magic pixie dust you find in some boxes of cereals and not others.
Scalability is extremely application specific. As your application grows, what will be the bottleneck? Maybe it's page-serving performance. Maybe it's the database. Maybe it's disk storage. Maybe it's synchronization of data. Maybe it's raw bandwidth. With no specific knowledge of your constraints, any specific advice is worthless and potentially harmful.
The question you need to ask yourself is not "which framework should I use?" but "how should I architect my application to ensure that the most likely bottlenecks can be resolved simply when I get there?"
If your likely bottleneck is bandwidth, for example, building your application with eventual use of a CDN in mind is probably very smart. If your likely bottleneck is disk storage, make sure you choose a host/infrastructure that allows you to scale that up practically indefinitely. If your likely bottleneck is page rendering performance, make sure you write very clean, unoptimised code, so that when the bottlenecks show up it's a simple matter to boost them without impacting the rest of the application.
- owkaye 18y ago"Scalability isn't a magic pixie dust you find in some boxes of cereals and not others. Scalability is extremely application specific." Absolutely correct. I have an app that is not scalable in most of the traditional ways because one live memory based database needs to be fast, have very large capacity, and be instantly accessible to all users concurrently. This appears to require a custom coded C program whereas the front-end web servers are a minuscule issue in comparison.