This is an American software development company that is best known for developing augmented reality games such as Pokemon Go and Ingress. These games are developed at the for the front of Technology Making the most of the new booming business of Augmented reality.
When the Pokemon Go game was first released, they fist aimed to get 1X traffic, This means that they first assumed that it would get 1 data store transitions per second. I fair feat at that, this case assumption was that at they would roughly get 5X. But due to the sudden popularity, the game surged to 50X the original estimate. This was over ten times the worst case estimate, causing issues.
Due to the enormous amount of unforeseen traffic, issues arose at launch, these issues were with the stability of the game. With Niantic and google’s engineers, they addressed the issues one by one working tirelessly, to create and then release patches. Googles new initiative Google CRE (Google: Customer Reliability Engineering, or CRE) allowed Google to work alongside with the Niantics team. Google put forward their own expert engineers and product managers, to Tirelessly working side by side with Niantic.
Pokemon Go was deployed from containers, This is one of the biggest examples of ” container Based development” that is currently working. Google has its own Container services called Google Container Engine (GCE) that run on the Kubernetes O/s. Niantic chose container deployment because it’s easy deployment in clusters. This allowed The team at Nainatic to easily automatic there system due to clustered containers. These containers acted like a readily made mold of their system ready to be copied and reproduced in a scalable environment as needed. This then allowed the Niantic team to focus on their live development of the highly popular game to keep ratings up.
One of the major issues of using this system was that the implementation team at Niantic & Google. Wanted to update the container system, to a newer improved system. This implementation was to allow 10000 additional Nodes for the container Clusters. In preparation for the release of Pokemon go in more country . the game’s change over to the newly updated containers was done carefully to not disrupt the original user base.
In the implementation plan, they also updated the network load balancer for the clustered containers, this needed updating due to their incorrect assumptions for the traffic load. They required a more complex load balancer that was more secure, they choose the Https load balancer because it’s more developed for worldwide applications. Aswell as the Https encryption, meaning that the game would be more secure. This also had faster connection rates for users meaning more connections, and furthermore, additional users for the Pokemon go game.
So in reflection Niantic Encountered Issues due to their original assumptions about the traffic flow to their newly released Pokemon Go game. They built their container system around their assumption of 1X traffic, But due to games high traffic rates the game had instance issues on launch that required immediate action. Both companys Google and Niantic came together to work through the issues and develop a better system. The clustered containers were updated to a newer version with more nodes for a more flexible system, as well as updated the load balancer with one that includes encryption and is designed for worldwide.’
This is a NewZealand organization that has been operating since 1960’s, this was launched back when we all had landlines, and it was a physical book that housed everyone’s numbers. I remember the time where we all had at least two landlines, one that was wired for when we had no power and one that was “fancy” and wasn’t plugged in.
But back in 2015, the times had changed, and it had become the time for a new change. The change was to become cloud based, they had an internet based company, but due to the times, they deiced to put their ingratitude into the cloud.
The yellow pages then proceeded to Look around at the different vendors that supplied cloud-based products but then proceeded to chose Amazon Web services due to the services they offered. Those services are of which that follows; IT structure automation, Self-service features as well as pay as you go pricing models. The yellow pages like these due to the minimal technical, financial and commercial risks.
“It was clear AWS was the right fit for Yellow New Zealand because of its industry experience, flexibility of service, enhanced security, and platform maturity,”- Rob Hayden, cloud infrastructure manager at Yellow New Zealand.
The yellow pages had then fast-tracked the implementation of the AWS infrastructure with the initial help of an AWS cloud solution specialist alongside with local technology partners. This overall took 9 months to implement. This was then followed up by migration of a wide range of applications, and after that cloud services team that still continues to offer help after implementation.
The yellow pages had seen many benefits of the cloud implementation, Some of them include the following; Cloudformation for application deployment with the help of Lambda for code based deployments and the use of EC2 container services to release new automated code into their system. Their traditional views have allowed AWS to integrate new IaaS approach for their infrastructure.
The business now can use the IAM roles to create new easy-to-understand platforms ready to use by their original Operations Staff. Without needing any addition extensive educating, as an addition, the users can easily look up Information that is stored by the Amazon Elasticashe instances.
So in reflection, The yellow pages have managed to create itself all over again, by moving from a physical book into a completely online cloud automated world. This was done by Vetting several different cloud vendors, and finally settling on AWS due to their longevity and low failure rates making them secure, flexible and reliable. That gives the yellow pages a Faster automated system that now can implement new digital products in minutes as opposed to the weeks with the previous method. For this reason, The yellow pages have managed to reduce costs and furthermore improved performance, allowing The yellow pages to migrate six production Applications over the AWS.
“In migrating Yellow and White Online—our core applications—to AWS, we gained a world-class application-delivery capability built on the latest technologies and best practices,” says Hayden.