|
|
| Author |
Message |
|
Charle
#1 / 7
|
 Scaleability
What does it mean to say that an application is "scaleable"?
|
| Tue, 14 Sep 2004 07:36:57 GMT |
|
 |
|
DLM
#2 / 7
|
Scaleability From TechWeb.com:
Refers to how much a system can be expanded. The term by itself implies a
positive capability. For example, "the device is known for its scalability"
means that it can be made to serve a larger number of users without breaking
down or requiring major changes in procedure.
Quote: > What does it mean to say that an application is "scaleable"?
|
| Tue, 14 Sep 2004 07:50:18 GMT |
|
|
|
Charle
#3 / 7
|
Scaleability Right, but in terms of application development, what makes a application
scalable, Is it distributing the workload over multiple clients rather than
centralizing it on the server? What development concepts are involved in
createing scalable applications? Give me some buzz words that I can
research....
Quote: > From TechWeb.com: > Refers to how much a system can be expanded. The term by itself implies a
> positive capability. For example, "the device is known for its
scalability"
> means that it can be made to serve a larger number of users without
breaking
> down or requiring major changes in procedure.
> > What does it mean to say that an application is "scaleable"?
|
| Tue, 14 Sep 2004 10:31:09 GMT |
|
|
|
Larry Linso
#4 / 7
|
Scaleability Generally it just means "can be scaled to handle more
users|queries|transactions, etc.". It almost never means spreading workload
over _clients_ but often means spreading workload over many servers.
Quote: > Right, but in terms of application development, what makes a application > scalable, Is it distributing the workload over multiple clients rather than > centralizing it on the server? What development concepts are involved in > createing scalable applications? Give me some buzz words that I can > research....
> > From TechWeb.com:
> > Refers to how much a system can be expanded. The term by itself implies
a
> > positive capability. For example, "the device is known for its
> scalability"
> > means that it can be made to serve a larger number of users without
> breaking
> > down or requiring major changes in procedure.
> > > What does it mean to say that an application is "scaleable"?
|
| Tue, 14 Sep 2004 10:45:48 GMT |
|
|
|
Joe
#5 / 7
|
Scaleability Quote:
> What does it mean to say that an application is "scaleable"?
"We are trying to market this POS to the Fortune 500"! It is also
needed before attempting to belittle the competition by claiming
their products are "not scaleable", usually without presenting any
justification. After all, nonexistent evidence cannot be refuted.
--
Joe Foster <mailto:jlfoster%40znet.com> Space Cooties! <http://www.xenu.net/>
WARNING: I cannot be held responsible for the above They're coming to
because my cats have apparently learned to type. take me away, ha ha!
|
| Tue, 14 Sep 2004 10:57:59 GMT |
|
|
|
Jason Bouzan
#6 / 7
|
Scaleability
Quote: > What does it mean to say that an application is "scaleable"?
There are lots of ways to make an application scalable, and distributing it
over a number of servers is only one solution. Another solution is threading
it properly so it can run on multiple processors, or it might simply mean
writing efficient code or porting to C++ (sorry, couldn't resist) :-).
Basically, it's a buzz word that means the application is written in such a
way that its usage can be increased without major problems developing in
functionality and responsiveness. Generally, if you write efficient code
that's well thought out, it should be fairly scalable.
Jason Bouzane
|
| Tue, 14 Sep 2004 14:49:45 GMT |
|
|
|
cml
#7 / 7
|
Scaleability The biggest keyword (buzzword) to research is n-Tier. One approach to
making lets say a database application n-Tier is the use of Microsoft
Transaction Server. You can build components that are hosted in Microsoft
Transaction Server that handle the business logic of the system and database
interaction, then build a client interface that just uses those components
(which are hosted on other servers). The client makes requests to those
components, those components that are now on another server (not the client)
handle the workload and they make calls to the database (which can be on yet
another server). When the number of clients requesting work from components
on the servers grows and starts to become a resource problem, you simply
load balance that server with other servers thus allowing your application
to "scale" without having to alter you code at all, all you did is throw
more hardware at the problem and balance the workload across multiple
servers. This is just the basic idea behind it.
HTH
--
Clint LaFever
http://vbasic.iscool.net
----------------------------------------------------------------------------
-
http://vbasic.iscool.net
Home of:
The Extended ListView (Edit any subitem) Free
The Code Depot Add-In
Much more (All Free)
----------------------------------------------------------------------------
-
Quote: > Generally it just means "can be scaled to handle more > users|queries|transactions, etc.". It almost never means spreading workload > over _clients_ but often means spreading workload over many servers.
> > Right, but in terms of application development, what makes a
application
> > scalable, Is it distributing the workload over multiple clients rather
> than
> > centralizing it on the server? What development concepts are involved
in
> > createing scalable applications? Give me some buzz words that I can
> > research....
> > > From TechWeb.com:
> > > Refers to how much a system can be expanded. The term by itself
implies
> a
> > > positive capability. For example, "the device is known for its
> > scalability"
> > > means that it can be made to serve a larger number of users without
> > breaking
> > > down or requiring major changes in procedure.
> > > > What does it mean to say that an application is "scaleable"?
|
| Wed, 15 Sep 2004 02:16:12 GMT |
|
| |
|
