Related Posts
Can data science help insurance to gain a competitive edge
Insurance is one of the largest industries globally, in terms of... read more
Is the Old way or New way better?
“Manjiri, the client wants these reports urgently. They have an important... read more
Have you utilized your strategic break productively?
“So Makarand, how was your strategic break last week? Did you... read more
5 Ways VoiceAI is Revolutionizing Healthcare
1. Medical Documentation: Healthcare providers spend significant time on medical documentation. VoiceAI... read more
Voice AI for Agriculture: Enhancing Farming Practices
Voice AI is transforming agriculture with its revolutionary technology. With the... read more
Technology Integration
#TechnologyIntegration is not just a buzzword anymore, but a key to rapid... read more
The Future of Finance Industry with Voice AI: An Expert Roundtable Discussion
As Makarand opens the discussion, how do you envision Voice AI... read more
The Future of Education Industry with VoiceAI: An Expert Roundtable Discussion
1. Enhanced Personalized Learning VoiceAI in education has the potential to provide... read more
How can trust and user adoption be built in VoiceAI-enabled customer service products?
1. Transparency in Data Usage: Clearly communicate to users how their data... 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?