Book Image

DevOps with Windows Server 2016

Book Image

DevOps with Windows Server 2016

Overview of this book

Delivering applications swiftly is one of the major challenges faced in fast-paced business environments. Windows Server 2016 DevOps is the solution to these challenges as it helps organizations to respond faster in order to handle the competitive pressures by replacing error-prone manual tasks using automation. This book is a practical description and implementation of DevOps principles and practices using the features provided by Windows Server 2016 and VSTS vNext. It jumps straight into explaining the relevant tools and technologies needed to implement DevOps principles and practices. It implements all major DevOps practices and principles and takes readers through it from envisioning a project up to operations and further. It uses the latest and upcoming concepts and technologies from Microsoft and open source such as Docker, Windows Container, Nano Server, DSC, Pester, and VSTS vNext. By the end of this book, you will be well aware of the DevOps principles and practices and will have implemented all these principles practically for a sample application using the latest technologies on the Microsoft platform. You will be ready to start implementing DevOps within your project/engagement.
Table of Contents (20 chapters)
DevOps with Windows Server 2016
Credits
About the Author
Acknowledgments
About the Reviewer
Acknowledgments
www.PacktPub.com
Customer Feedback
Preface

Azure public load balancer


A public load balancer is attached to all web application virtual machines for sending requests to them in a round robin fashion. A public IP address and DNS name is assigned to a load balancer for accepting Internet requests. Although it can accept requests on any viable port, for the purpose of the sample application, it accepts HTTP web requests on port 8080 and routes the same to the virtual machines. It also probes on port 8080 on HTTP protocol with /newapp/Index as its path. The sample Online Medicine application can be browsed using the http://<<public ip address of load balancer>>/newapp/Index URL. Couple of Network Address Translation (NAT) rules are also opened so that they can be used to log in to the virtual machines using a remote desktop.

An alternative resource to the Azure public load balancer is the Azure application gateway, and depending on the scenario, this can be used and deployed. Again, it should be noted that port 8080 is configurable...