Hey You – Case Study

Customer Details

Hey You is an Australian startup that connects to over 1,300 cafes and restaurants, serving more than 600,000 unique users. The simple and friendly Hey You interface allows users to order their morning coffee or lunch with a few taps on a mobile app, avoiding the need to wait in crowded lines. Hey You have a vision to revolutionise ordering and payment across the world, with their focus on connecting customers to businesses.

Business Needs

After significant business growth, Hey You required increased automation to help scale with the number of users and restaurant partners joining their platform – without suffering an increase in cost.

We wanted to configure the correct tooling setup for our business and implement automation and DevOps practices to enable our developers to move away from manual processes and optimise the management and maintenance of our environment.

Without a DevOps team in place, we decided to bring in an experienced external partner with the right mindset and approach to set up the environment correctly.

Solution

PolarSeven automated the continuous deployment pipeline drastically reducing time to deploy new code into production. The new environment allows for triggered automated deployments and automatic scalability of the application stack.


What solution did PolarSeven implement for Hey You?

One of the core requirements of the production environment was to ensure the boot time of new Amazon EC2 instances is as fast as possible. This was driven by the sporadic use by Hey You customers and the traffic profile (application gets a lot of flash traffic) on the V2 API application stack.

Due to this requirement, it was decided to bake everything into the Amazon Machine Images (AMI) for deployment to production environments.

All other environments (test, staging) remain consistent with production by executing the same scripts and deployment process using AWS CodePipeline and AWS CodeDeploy. Continuous deployments are executed on a commit trigger on the ‘develop’ branch.

All infrastructure from each application stack, continuous deployment pipeline and build or deployment services are provisioned using AWS Cloudformation and committed to source control.

What specifications needed to be adhered to?

The AWS Security Best practices were an important consideration when creating the environment, ensuring there was no manual configuration that result in back doors into the environment, and to provide a fully automated and scalable environment.

Project Outcomes

  1. Fully automated deployment on staging and production
  2. Autoscaling on instances
  3. Significant reduction in running costs of the environment:
    • Saving of 10 C4 large servers per day
    • The project paid for itself in approx. 3 months

Cultural benefits of the new environment

  • Improved workflow
  • Easier deployments
  • Automated testing
  • Fast rollback to previous versions

Other benefits

Request numbers on the environment are the same but CPU on servers is running much lower, around 10% more efficiently.

  • Client Hey you
  • Date August 15, 2019
  • Tags Start-ups
  • URL View Project