13Oct
Related Posts
12Jul
5 Ways VoiceAI is Revolutionizing Education Industry
1. Personalized Learning Experiences VoiceAI enabled personalized learning by analyzing speech patterns,... read more
19Jul
Start now if you want to get it done!
“Don’t perform tasks in sequence, when they can be done in... read more
23Apr
Data Strategy: A strategic asset
Mckinsey just came out with a study that found that the... read more
24Feb
No one is born with a silver spoon!
Providing the right #opportunities to those who want to excel in life is... read more
28Apr
Are you delivering promised value
Is your product really delivering the promised value? No one will be... read more
06Sep
Calculated Risks – Secret Sauce to Success
“The difference between courage and stupidity is measured by success and... read more
03Dec
Growth V/s Retention
When large companies plan for further growth, technology changes are necessary,... read more
01Jun
Command on Command Line
Being a Software Engineer is not just writing code, debugging, and... read more
“We will use it from next week. Will it hold well when all users log in on Monday morning?” A common concern, based on past experience.
The team had done a good job of understanding the scalability requirements, designed an architecture that will scale well. However, during the initial phase, everyone was focused on functionality. Performance was yet to be tested.
As I was reviewing, I found one thing missing – concurrency requirements.
How many users can be active at the same time?
How many requests will simultaneously reach the server?
This is an essential factor for capacity planning. Too less will mean dropped requests and too much will mean higher costs.
There is no correct answer. Concurrency keeps changing based on external events, time of the day, user behavior, etc. It can be predicted only with visibility into past data.
This is where instrumentation comes to help. Build desired counters in the system, record, monitor, and notify them regularly. Allow for the tuning of what to check, what to record, and what to notify. You are going to need regular monitoring and tweaking for the best efficiency.
Do you have the counters built in your product?