Developer shares key design decisions and fixes in cinema seat reservation system
A developer building a cloud-native, microservices-based cinema seat reservation system on ASP.NET Core documented two significant performance problems encountered during load and stress testing. One endpoint for fetching showtimes with filters recorded a latency of around 850ms, partly attributed to network overhead between servers in different countries. During stress testing along the system's critical request path, P95 latency spiked to 16 seconds, a level likely to cause users to abandon their sessions. Common solutions like database indexing and caching were explored but found ineffective or counterproductive, particularly due to the variable nature of range-based date queries. The developer has shared detailed architectural decisions and trade-offs in the project's GitHub repository for others to reference.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in