The need for Managed Cloud Services

HOOQs Challenges

• 

  Accommodate Growing Demand

  The customer’s need of the hour was to redesign its infrastructure to support the increasing demand.

• 

  Manual Deployments

  Manual deployments were prone to human errors, and the maintenance window (~ 40 mins) was relatively high.

• 

  Monolithic Architecture

  With its overall Monolithic architecture, any change in the older module would require redeployment of the entire application, rendering scaling an uphill task.

The Expectations

Collaborating with CloudCover for scalability, automation & cost optimization.

The customer realized that with specific infrastructure improvements, they would meet end-user demands quickly and scale massively. The ultimate goal was to automate the process, save a substantial amount of time and help them achieve king kong scalability in a highly available and reliable environment.

Solution

Technical Solution Decoded

• 

  Automated Deployments

  A simple yet powerful combination of Jenkins and Ansible eased out scheduling deployments. CloudCover automated all their Jenkins jobs (using in-house bot ‘CeCe’) for every service based on AWS.​ In some instances where deployments failed, rollback requests were initiated automatically. Twilio sends notifications and alerts when a deployment fails & triggers a rollback.

• 

  King Kong Scalability

  CloudCover facilitated customers’ move from a Monolithic architecture to a Microservices model to improve their scalability. They were witnessing situations where one application feature experienced a rise in need, and the entire architecture had to be scaled; this, in turn, affected other services’ performance. CloudCover isolated the services into different services and reduced the risk of a single point of failure. CloudCover applied the ECS containerization technique and deployed Application containers for running a microservices application architecture.

• 

  Launch New Services With Ease

  For launching any new service, CloudCover utilized Terraform to provision resources, ranging from service (including Amazon EC2, ELB, RDS, Amazon S3) to an entire infrastructure on AWS.

• 

  Cost Optimization ($$$)

  CloudCover regularly performed inventory checks that identified idle and unused resources to spot areas for cost optimization. With CloudWatch alarms (integrated with Slack and email), you can monitor services effectively. CloudCover set up AWS Instance Scheduler so that the EC2 and RDS Instances are turned ON/OFF for Dev, staging, and testing environments based on a defined schedule.

The Architecture Diagram