By bloid
via use.perl.org
Published: Oct 13 2008 / 01:30
Most programmers are working on projects where scaling and speed just aren't all that important. It's probably a webapp with a database backend, and they're never going to hit the point where any "standard' component becomes an insoluble bottleneck. As long as the app responds "fast enough", it's fine. You'll never need to handle thousands of request per minute.
-
Why you should write tests before code
-
Generic delegate in C# 3.0 or .NET 3.5
-
Mapeamento objeto-relacional: o problema das tabelas associativas
-
Repetitive Calls to Find the Same Element Using document.getElementById and Performance
-
Throwing undeclared checked exceptions
-
Give us feedback on Silverlight 2!
Comments
Loïc Hoguin replied ago:
I'd recommend reading the opposite POV too.
http://devzone.zend.com/article/3884-Scaling-Day-By-Day
Scaling is really not that hard if you are doing it since the beginning of the project, and if you have tools to help you keep detailed informations about performances in your application.
Of course, smaller projects don't necessarily need to scale. But you never know that the small app you developped just now is going to get used by thousands of people in just a few years because your company had a good growth. Sometimes, taking a few hours to ensure your app is efficient will pay off in the end by not having to buy 50K$ of servers.
The answer is not to not scale. The answer is to automate scaling tests. That's my opinion anyway.
Voters For This Link (7)
Voters Against This Link (2)