What is Scalability?
A feature of DVD-A that allows the producer to select from various sample rates (44.1, 48, 88.2, 96, 176.4, and 192kHz) and word lengths (16, 20, 24). It is also possible for the producer to assign different sample rates and word lengths to different channel families, such as 96/24 to the front speakers and 48/16 to the surrounds. Once again, this feature sounds better than it really is. It’s a production hassle to have different channels at different word lengths and sample rates and some of the DVD-A authoring software doesn’t implement the feature anyway.
When asked what they mean by scalability, a lot of people talk about improving performance, about implementing HA, or even talk about a particular technology or protocol. Unfortunately, scalability is none of that. Don’t get me wrong. You still need to know all about speed, performance, HA technology, application platform, network, etc. But that is not the definition of scalability. Scalability, simply, is about doing what you do in a bigger way. Scaling a web application is all about allowing more people to use your application. If you can’t figure out how to improve performance while scaling out, its okay. And as long as you can scale to handle larger number of users its ok to have multiple single points of failures as well. There are two key primary ways of scaling web applications which is in practice today. • “Vertical Scalability” – Adding resource within the same logical unit to increase capacity. An example of this would be to add CPUs to an existing server, or expanding storag
Related Questions
- Im worried about scalability. What happens if Wikibooks is invaded by hordes of new people who don understand whats going on here, and mess it up?
- How will the current KNETMAP QofWeek application respond to scalability, for example, on a population of 5000 nodes?
- What type of constraints does GAE place around application scalability?
