Welcome » Case Studies » Tele Ticket Service – Migration To AWS
AWS CASE STUDY
TELE TICKET SERVICE:
MIGRATION TO AWS
Tele Ticket Service wanted to migrate their entire online ticketing system (running in a local datacenter) to the AWS Cloud. We were more than happy to help them with that…
CUSTOMER:
Tele Ticket Service
PROJECT:
LAUNCH:
December, 2019
Customer Profile
Tele Ticket Service is a full-service ticketing agency based in Antwerp. The company was founded in 1986 with the first major customer being the music festival Night of the Proms. Thanks to the confidence of thousands of customers and organisers, the technological innovations of the past few years and the experience built up over thirty years, Tele Ticket Service has grown into the market leader in Flanders.
The Challenge
The Tele Ticket Service environment in its whole is quite large. It consists of three environments: development, staging and production. Multiple third-party companies work together to get the application up and running smoothly. Moving an application like this takes quite a lot of coordination between all parties. Especially because it is a very critical application for the company, that must be able to handle a lot of load in a short period of time.
Our Solution
We’ve chosen to set up a relatively static environment for this project, as the application itself is not able to work with scaling infrastructure. The production environment is quite extensive, the other environments have multiple functions put together on single machines to save costs. The sections under management of different companies each have their separate infrastructure, and the necessary communication between them is allowed.
- Amazon ELB is used to balance traffic across the instances.
- Amazon RDS Backend, spread across multiple availability zones for high-availability.
- Amazon S3 object storage for static files.
- Amazon CloudFront for edge caching, to reduce overall load on the system by caching where appropriate.
- AWS CloudTrail to monitor the IAM actions taking place on the account.
We also made use of a number of AWS technical partner solutions:
- CloudCheckr© was used to ensure the setup complied with AWS best practices and to ensure ongoing compliance once the solution was in production.
- This infrastructure was managed using AWS CloudFormation, both code and infrastructure were deployed on AWS using Jenkins Pipelines making use of CloudBees© Jenkins plugins.
- Site24x7© was used in conjunction with AWS CloudWatch to ensure optimal performance across all environments.
The Result
PERFORMANCE
AWS is an ideal platform for these kinds of applications that have heavy loads in short periods of time.
MULTIPLE ENVIRONMENTS
By using Infrastructure-as-code it is very easy to set up multiple similar environments.
EVERYTHING CLOUD
TTS is striving to have all their applications hosted on the cloud. This project got them closer to that goal.