Cox and Kings-Migration and DevOps Consulting

Customer Profile

 

Cox & Kings is the longest established travel company in the world. Its distinguished history began in 1758 when it was appointed as general agents to the regiment of Foot Guards in India under the command of Lord Ligonier.

Their worldwide offices are located in UK, USA, Japan, Russia, Singapore, and Dubai. It has associate offices in Germany, Italy, Spain, South Africa, Sweden, and Australia.

 

The Challenge    

 

Cox and Kings undertook a business transformation exercise and was evaluating to use AWS and its services to gain a competitive edge.

They have selected SAP Hybrid on HANA, Oracle Middleware and Oracle Coherence as the stack. SAP consulting was selected as the implementation partner for the project and CNK was looking for an infrastructure partner. CNK evaluated multiple partners including local data centre providers and SAP HEC. Based on the value proposition CNK selected Blazeclan to as infrastructure partner.

 

The Solution      

 

The BlazeClan team of certified SAs conducted an exhaustive study of the system and charted out a roadmap for deploying their SAP Hybris on AWS.

The team helped Cox and King to deploy the SAP Hybris Commerce, Marketing & Billing with SAP HANA database on AWS EC2 and Oracle SOA as middleware on AWS. This was fairly a large deployment of more than 300 Instances and using multiple AWS services including but not limited to EC2, EBS, S3, ELB for HA and Auto-scaling, ElastiCache, VPC, IAM, CloudWatch, etc.

There were four environments including dev., QA, pre-prod & prod. The team also helped in the auto scheduling of application and database instances by writing custom scripts. This reduced their cost tremendously.

 

DevOps based approach

 

  • The team undertook a DevOps based approach for infrastructure automation. They created templates for deploying each component of the infrastructure making it more flexible and scalable.
  • Deployment/provisioning of Cox and Kings production, staging, and development environments on AWS was executed using AWS CloudFormation.
  •  Deployment and monitoring of the entire infrastructure on all the environments was executed by leveraging the following DevOps tools like GIT, Sonar, and Jenkins.
    • Gitlab: A free repository tool which provides features such as code reviews, issue tracking, activity feeds and wikis was used keeping in mind the huge team size that was working on this project.
    • Jenkins: This tool was mainly used to generate builds automatically and also to maintain continuous integration.
    • Sonar: An open source platform was utilised for keeping a code quality.
    • Zabbix: An open source monitoring tool was used to check all the parameters and keep a check on the overall performance of the system.

 

DevOps Flow diagram

Cox and Kings Architecture

The Benefits  

 

1. Improved Performance: The entire system was deployed in Auto scaling mode and hence CNK would be able to scale during peak time using the auto-scaling functionality of AWS.

2. Cost Savings: this engagement brought about massive cost savings as payments needed to be made only for actual usage.

3. Lower financial risk: BlazeClan team helped in reducing the company’s financial risk by moving from a CAPEX based to compete with OPEX. The customer is now utilising the agility of the system by running dev. systems only for 10 hours a day, 6 days a week.

 

Tech Stack

 BlazeClan availed a number of AWS services to execute this project successfully.

 

  • Amazon EC2 was used for compute 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 VPC helped in setting up the private network with AWS as it provided isolation and security.
  • AWS CloudFormation was used in the production/development/UAT environments for mirroring purposes for automated deployments.
  • Amazon Machine Image was used to spin new instances for creating infrastructure
  • Gitlab: A free repository tool which provides features such as code reviews, issue tracking, activity feeds and wikis was used keeping in mind the huge team size that was working on this project.
  • Jenkins: This tool was mainly used to generate builds automatically and also to maintain continuous integration.
  • Sonar: An open source platform was utilised for keeping the code quality.
  • Zabbix: An open source monitoring tool was used to check all the parameters and keep a check on the overall performance of the system.

Discuss Your Cloud

captcha