After the release of the first version of TicketMonster, it was based on a traditional architecture. Let's imagine, that our application has grown enough to force changes in the current architecture. Due to the great growth of transactions in our system, TicketMonster starts decreasing the performance of the system.
In order to keep running TicketMonster without losing quality of service, we will need an environment that meets the following requirements:
High Concurrency: During high season, weekends, special events, or show, tickets can be sold out in 5 minutes
High Volume: Depending of the venue and show, we can have thousands of tickets
Location Awareness: Shows can take place all around the world, and we'd like the data to be available in the same region as where the show will be taking place (such as concerts in London and New York)
Furthermore, with the imminent success of TicketMonster, our customers are asking us to add new features such as the ability to reserve...