Book Image

Implementing DevOps with Microsoft Azure

By : Mitesh Soni
Book Image

Implementing DevOps with Microsoft Azure

By: Mitesh Soni

Overview of this book

This book will teach you all about the Visual Studio Team Services and Microsoft Azure PaaS offerings that support Continuous Integration, Continuous Delivery, Continuous Deployment, and execution in the cloud with high availability, disaster recovery, and security. You will first be given a tour of all the concepts and tools that Microsoft Azure has to offer and how these can be used in situations to cultivate the DevOps culture. You’ll be taught how to use and manage Visual Studio Team Services (VSTS) and about the structure of the sample application used throughout the book. You will become familiar with the nitty gritty of Continuous Integration and Continuous Development with VSTS and Microsoft Azure Apps. You will not only learn how to create App service environments, but also how to compare Azure Web Apps and App Service Environments to deploy web applications in a more secure environment. Once you have completed Continuous Integration and created the Platform for application deployment, you will learn more about the final stepping stone in achieving end-to-end automation using approval-based Continuous Delivery and Deployment. You will then learn about Continuous Monitoring, using the monitoring and notification options provided by Microsoft Azure and Visual Studio Team Services.
Table of Contents (17 chapters)
Title Page
Credits
About the Author
Acknowledgment
About the Reviewer
www.PacktPub.com
Customer Feedback
Dedication
Preface
More from the Author

Overview of agile in VSTS


Agile principles have changed the game in recent times. Because of the feature-wise implementation and short sprints, delivery of the application becomes extremely faster. An end-to-end discussion on agile is out of the scope of this book; however, we will try to give a brief summary.

There are different phases in SDLC, and traditionally, all those phases are managed or executed in a sequential manner—the waterfall model. The problem with this model is that it is in sequence and a one-time activity; each phase takes a lot of time and changes are not easy. Feedback from the customer take so long that at the end of all the phases, we as developers are not sure whether we have implemented the same product that was intended and communicated by the customer or there was a communication gap. The ideal way to deal with this is to provide frequent delivery to the customer for a few features and receive frequent feedback to fix things or innovate. The visible benefit is this...