Serving millions of customers during significant events, such as a popular show or live sports events, is crucial. Customers expect a fast, responsive and seamless experience, and slow responses or unavailability can lead to frustration, dissatisfaction and loss of trust.
It is hard to predict the number of requests because several factors can influence it, such as the event’s popularity, the marketing efforts. We expect that there might be a spike in requests in a short time.
This unpredictability can lead to slow responses and a bad user experience because the system may need help to handle the sudden increase in traffic. If we do not design the system to handle high loads, it may become overwhelmed and unable to respond to requests on time. This can lead to long waiting times, errors and even crashes, resulting in a poor customer experience and damaging the brand’s reputation.
To prevent these issues, it is essential to design and implement a robust and scalable system that can handle sudden spikes in traffic.
With a Serverless First mentality, our engineering team is always looking to experiment with the latest serverless technology to solve the continuous needs of better scalability, faster response, and less infrastructure maintenance.
But in reality, it may turn out that Serverless Applications are subject to many limitations, and therefore we talk about event-driven architectures(EDA). This talk will show the relationship between best practice and scalability in a synchronous application scenario, ending with an EDA application.
Can a Serverless application scale? The short answer is it depends on the workload. However, several strategies can minimize latency and impact the application’s scalability. If you are wondering what the effects of best practices on a serverless application are, this talk will show the correlation between best practise and scalability.