Talk:Scalability VAG

Current State of Play

• New section added. --Morgaine Dinova 08:57, 12 November 2007 (PST)

Specific concerns within this viewpoint

• I've purposely placed this section after Dimensions of scalability and not immediately after General concerns addressed by this viewpoint so that the "Dimensions" can act as a first-order template for the specifics.

Members (Stakeholders)

• Welcome, Jesrad. :-)

FYI the current state of play in this VAG is something like this:

• We don't know exactly what to analyze for scalability in the new arch until we know how the resources are partitioned into REST services. Afaik, candidate partitionings haven't been proposed yet either, so this is on hold unless someone wants to kickstart the process with some proposals. I assume this will happen in the REST Services VAG.
• Some tools were deemed appropriate for applying actual workloads to the reference implementation of REST services so that we could spot descaling trends early on. That work is in progress in the Multi-Process Client VAG -- draft, and despite that still being in draft form and in early design state, there is reasonable progress there. (Feel free to join. :P)
• I started but did not complete my analysis of mitigating factors that reduce the arithmetic scalability requirement of regions to below that calculated in Project_Motivation. I must do this. All help welcome. :P --Morgaine Dinova 08:40, 12 November 2007 (PST)