Related Posts
5 Game-Changing Trends in Software Product Engineering for 2023
Excited to share the scoop on the game-changing trends that are... read more
Delegating can make you a better leader
“‘You need to make yourself redundant in your current job, to... read more
How to define your AI goals
Failure to define AI goals is one of the main reasons... read more
How do you prefer to measure the productivity?
“Whenever I need to talk to you, you have never said... read more
Voice AI for Nonprofits: Transforming Fundraising and Donor Engagement
In today's digital landscape, software industry leaders are seeking innovative ways... read more
Clarity for the Leadership
“I can see a gap between what formal education provides and... read more
Succession planning: the importance of planning early
Yash, have you thought about who will run your business after you?” “Are... read more
setting a priority
“Would you like to have another burger?” Deepak was surprised by... read more
The Art of Code Refactoring: When, How, and Why You Should
Today, let's dive into the world of code refactoring – a... read more
The Journey of Conversational AI and the Rise of Chatbots and Virtual Assistants
In the dynamic landscape of artificial intelligence, the evolution of conversational... 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?