Part 2: Number Concurrent users and performance requirements

[Vlad Eroshin]

How requirements to number of concurrent users affects design? Should we calculate how many server clones to put? Or why do they mention it in the assignment?

Please advise.

Thank you very much.

Vlad

[J Davidson]

Resource contention is your biggest issue. Do you have enough threads/nodes handling concurrent requests? Do you have beefy hardware to support your system? You must look at the whole system from the GUI down to the hardware.

[Vlad Eroshin]

Thank you very much, J!

Does this mean that I should calculate thread and connection pools sizes on the Application server. If that the case where should I put this information in the Assumptions section? Or my deployment diagram must reflect this info?

By the way, what is the good approach to calculate all this? Or just by looking on the specs of the Database and Application Servers.

Please advise,
Vlad

[Parag Bharambe]

I think the most challenging question is how one can quantify ?

How can one be assured that the system will support so many number of user?

Parag

[Andr� Salvati]

The answer is hard-work: build prototypes and use simulators and tools like JMeter until defining project architecture.

[Morten Franorge]

As the delivery is just uml and assumptions, isn't the only real option of answering the concurrent user requirement to design it scalable. So that it's easy to add servers as the number of users increase? Prehaps set up a quantity of servers in the deployment diagram?

[Newman Huang]

i think the big concurrent number means we should design a more flexible framework to meet the non-functional requrments. how to reach such a goal you can describe it in your design.