Related Posts
5 Key Strategies for Data Security and Compliance in a Multi-Cloud Environment
In the dynamic realm of cloud computing, multi-cloud environments have emerged... read more
Data Engineering Best Practices: Ensuring Data Quality and Integrity
In the fast-paced realm of data engineering, ensuring the quality and... read more
Employee Story – Sanatan
I joined #CoreViewsystems after a 3-year break from IT. Though I had a... read more
Regaining a momentum
“Laziness may appear attractive, but work gives satisfaction.” – Anne Frank “Good morning... read more
Multithreading programming- To be or not to be used
Every time we visit a crowded restaurant, it's astonishing to see... read more
5 Ways VoiceAI is Revolutionizing Education Industry
1. Personalized Learning Experiences VoiceAI enabled personalized learning by analyzing speech patterns,... read more
Labeled data rarely exists in the real world
Majority of the machine learning courses assume the availability of labeled... read more
Scaling Up: Securing Working Capital
“Makarand, I am all set for the next jump. I am... read more
Going global with amazon MWS-API
Introduction Amazon MWS provides a complete (well, almost complete!) web-based solution for... read more
The Future of Voice AI in E-commerce: 5 Trends for Creating Personalized Shopping Experiences
E-commerce is evolving rapidly, and voice-enabled technology is transforming online shopping.... 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?