In third year networking we do a lot of work that involves cloud providers such as Amazon Web Services (AWS). Seeing the amount of money businesses have saved by moving to more managed options in the cloud has prompted me to research this more. To do this i analyzed a case study where a New Zealand business made big savings by shifting over to the cloud.
Faster service delivery, easy scaling, and a consistent high quality of delivery is what Yellow based their decision on when moving to AWS in 2015. Only through a cloud solution could the company automate its IT, introduce self-service features, and take advantage of pay-as-you-go pricing models. Yellow New Zealand wanted to leverage public cloud offerings from organizations such as Amazon Web Services (AWS) to deliver the benefits and capabilities of cloud technologies with minimal technical, financial, and commercial risk.
Before choosing AWS, the planners at yellow already knew they wanted to move to the cloud to reduce costs and increase efficiency of its IT staff and systems. AWS was chosen over other considerations because of the technical, financial benefits and low commercial risk due to them being the main industry player (2015). Yellow differs from other case studies in that they worked extensively with an AWS solution architecht, Cloud specialist, and other parties to plan and undertake their switch to the cloud.
One thing Yellow was looking for in a cloud provider was the possibility for automation of tasks. Yellow currently takes advantage of AWS Cloudformation in conjunction with AWS Lambda to deploy and scale-up its applications and uses Amazon EC2 Container Service (ECS) to automate new code pushes and maintain versioning.
Amazon EC2 Container Service (Amazon ECS) is a highly scalable, fast, container management service that makes it easy to run, stop, and manage Docker containers on a cluster of Amazon Elastic Compute Cloud (Amazon EC2) instances. Amazon ECS lets you launch and stop container-based applications with simple API calls, allows you to get the state of your cluster from a centralized service, and gives you access to many familiar Amazon EC2 features. Cite http://docs.aws.amazon.com/AmazonECS/latest/developerguide/Welcome.html
Elasticache is another AWS offering which Yellow utilizes in its applications and it allows access/storage of frequently used data by users. The Elasticache instance in use runs Redis which is used as a data store, cache and message broker. “Combining code optimizations with Amazon Elasticsearch Service has made response times twice as fast for business searches carried out on its core website, Yellow online. ElastiCache is a web service that makes it easy to set up, manage, and scale a distributed in-memory cache environment in the cloud. It provides a high-performance, scalable, and cost-effective caching solution, while removing the complexity associated with deploying and managing a distributed cache environment. More information can be found at: http://docs.aws.amazon.com/AmazonElastiCache/latest/UserGuide/WhatIs.html
Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache and message broker. It supports data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs and geospatial indexes with radius queries. More information can be found at:
Availability – latency
Due to the multi-region support offered for many of Amazon’s services, Yellow was able to deploy their systems appropriate region (Sydney) to decrease latency times for their userbase in New Zealand. Yellow’s own datacentre in Auckland is directly connected to AWS using AWS direct connect using MegaPort which significantly decreases latency and increases throughput.