May 2015
Intermediate to advanced
464 pages
10h 19m
English
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:
Read now
Unlock full access