My definition of "scalable" is that it can serve more users, without
re-doing the application.

Mike Wills wrote:
Maybe your definitions are different than mine.

My definition of scalable is growing to more than one server. I don't know
what yours is.

"Throwing more hardware at a performance problem is not my idea of
scalability." The last I checked, you have to add more memory or add a CPU
to a IBM i to enhance performance as well. You can't take a low-end i and
expect it to process millions of hits an hour. The difference is that most
PC hardware don't support 32 CPUs or more. They are built cheap. So for the
cost of that additional web server, I have added another CPU and more memory
to my i. (Okay, so I don't know that is fully true, but it isn't cheap to
upgrade an i). So really, I AM throwing hardware at the problem. The only
difference is that we can get a system big enough that could handle those
high loads and keep a "single machine". Which from what I have seen these
days are still racks of servers (to the non-initiated).

Performance is different. Poor performance could be fixed with more
hardware, but most high-traffic sites throw hardware to temporarily ease the
problems it until they fix it permanently (like Twitter had to do).

Unless they know their site will see heavy use from launch, many developers
don't look at the issues in creating scalable sites until the problems show
up. Heck, I wouldn't know what to do on the i much less on Windows to make
things truly scalable.

--
Mike Wills
http://mikewills.me


On Fri, Oct 8, 2010 at 3:42 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

From: Richard Schoen
Actually going back to the original thread this is a good example
of scalability which in this case happens to be using Windows servers.

Adding more servers to a server farm is not my idea of responding to
increasing
workloads "gracefully". Throwing more hardware at a performance problem is
not
my idea of scalability. It's more a symptom that the system is NOT
scalable.
Anybody can add a new server and route requests to it.

Of course, Microsoft is working from a different play book.

-Nathan




--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.