Book Image

Mobile DevOps

By : Rohin Tak, Jhalak Modi
Book Image

Mobile DevOps

By: Rohin Tak, Jhalak Modi

Overview of this book

Today's world is all about perfection, and there are hundreds of applications that are released each day out of which only a few succeed. Making sure that the app looks, performs, and behaves as expected is one of the biggest challenge developers face today. The main goal of this book is to teach developers to implement DevOps to build, test, and deliver. This book will teach you to implement Mobile DevOps at every stage of your application's lifecycle with Visual Studio and Xamarin Mobile Lifecycle solutions. Later, it will also show you how to leverage Mobile Center's continuous integration and automated testing to develop a high-quality applications. Next, you’ll see how to mobilize your on-premises data to the cloud and increase your productivity with code reuse. Finally, you’ll discover how to find and fix bugs beforehand, improving the efficiency of your application while it is being developed. By the end of this book, you will be well-versed with Mobile DevOps techniques, delivering high quality and high performance mobile apps.
Table of Contents (13 chapters)

Summary

In this chapter, we looked at various methods of creating EC2 instances for our software deployment. Once an instance has been created, push the software jars into your instances. Use the private instance IP, username (ec2-user), and private key (test.pem) to connect to your machine. Once the testing is completed, make sure you terminate the test instances so you don't pay for them.

T2.micro EC2 instance type is free for use for one year for new AWS accounts.

Later on in the chapter, we went through the creation of ELBs and ASGs using AWS CLI.

You can register your ELB DNS name with your domain service provider (for example, Route 53, GoDaddy, and BigRock) to resolve your application.

You can also try putting some workload into your application and see whether Auto Scaling is increasing the number of instances, and then remove the workload to test the termination...