Founded in 1960, Domino’s is the largest pizza chain worldwide, with more than 10,000 corporate and franchised stores in 70 countries. Pizza is the primary focus, with traditional, speciality, and custom pizzas available in a variety of crust styles and toppings. In 2011, Domino’s launched artisan-style pizzas. Additional entrees include pasta, bread bowls, and oven-baked sandwiches. The menu offers chicken side dishes, breadsticks, as well as beverages and desserts.
Dominos’ order management system supports the major part of its business. While the customers could place orders through two interfaces – web and mobile, Dominos team was struggling with the performance issues of the order management system.
This mostly happened because many users’ browse menus and offers, but did not place an order and majority were not even logged into their system as customers. This resulted in high browsing load which the existing on-premise server could not handle. To combat the performance and scalability issues, Dominos wanted to migrate to AWS.
BlazeClan conducted an exhaustive study of the existing system and charted out a roadmap to migrate their order management system to AWS.
The team of certified SAs proposed the following solution to overcome this issue:
- Discovery of the existing architecture, assessing cloud readiness and designing of the AWS environment. This also included assistance in preparing the order management system cloud ready.
- Implementation of the AWS environment, setting up IAM user management and authorization authentication as per the underlying best practices. This also included migrating the order management system to AWS and setting up Cloud Front to provide a better browsing experience. Implementation of the auto-scaling groups with ELB to make the existing order management system highly scalable and elastic in nature.
- Testing of the order management system to validate support for 10s of thousands of concurrent users.
- High availability: Successful deployment of the order management system resulted in making the platform highly available in nature and now support 10s of thousands of concurrent users.
- Scalability: The Company achieved the ability to scale the application as and when required along with granular level control of the environment.
- Improved Performance: Migrating the application to AWS from the traditional data centre, helped in improved performance as it could easily scale and meet the needs of thousands of users and processed all transactions with low latency.
BlazeClan availed a number of AWS services to execute this project successfully.
- Amazon EC2 was used for computing capacity management for their application deployment. It helped in reducing the time required to spin up new server instances to minutes, allowing them to quickly scale capacity, both up and down, as per their requirement.
- Amazon S3 was used to store and retrieve any amount of data from anywhere and everywhere.
- Amazon RDS service was used to set up, operate and scale relational database and was mainly used for deployments.
- AWS NAT Gateway was used to allow instances in a private subnet to connect to the Internet or to other AWS services.
- ELK stack was utilised for log aggregation and analytics. It is a combination of Elasticsearch (a NoSQL database and search server), Logstash (a log shipping and parsing service), and Kibana (a web interface that connects users with the Elasticsearch database and enables visualisation and search options for system operation users). It helped in providing a centralised and searchable repository for all infrastructure logs, thereby providing a unique and holistic insight to the customer.