Related Posts
Employee Story – Pankaj
If you have the #passion to #learn... work at CoreView! One can grow professionally... read more
Labeled data rarely exists in the real world
Majority of the machine learning courses assume the availability of labeled... read more
Planning beyond the uncertainties
“The rest of this year (2021) will be full of uncertainties.” Was... read more
Machine Learning with Graphs
Complex domains have a rich relational structure which can be represented... read more
New Employee Story – Rajnandini
Who would have thought that within 2 weeks of joining I'd... read more
Forklifting existing Client-Server installations into The Cloud
In an era where users are demanding more flexibility and security... read more
Is everyone in your organisation motivated by growth?
“Growth means different things to different employees.” I was explaining to... read more
Did you hear of “Claude” – The new ChatGPT Alternative
Anthropic, founded by former OpenAI employees, has recently launched a new... read more
Streamlining Software Engineering with Serverless Architecture
In the fast-paced world of software engineering, the adoption of serverless... 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?