Finally, we are at the business end of the book, and our focus is on deployment, automation, monitoring, and orchestration. Why? It’s because we want to achieve end-to-end application lifecycle automation or end-to-end deployment automation. First, we will go step by step to deploy our PetClinic application to a remote Tomcat server. Once that is done, it can be used as common practice for all instances.
- Practical AWS Networking
- Learning Azure Functions
- Jenkins Continuous Integration Cookbook
- Jenkins Essentials – Second Edition
- DevOps for Web Development
- Implementing DevOps with Microsoft Azure
- DevOps Bootcamp
- Jenkins Essentials
This chapter describes in detail all the steps required to deploy our sample application to a different environment once the configuration management tool prepares it for the final deployment. We will also learn how to deploy the application in different environments, such as cloud or container-based ones. This chapter will also cover on how to deploy an application on a PaaS model. We will deploy the application on AWS Elastic Beanstalk.
We will cover the following topics:
- Prerequisite – deploying our application on a remote server
- Deploying the application on AWS
- Deploying the application on Microsoft Azure
- Deploying the application in a Docker container
Our main objective is to deploy application in a web server. Web server and application server can be on local environment or remote environment. We will first deploy on a remote server. We will try to use Windows Agent for compilation and deployment to see how Agent-based architecture can be utilized.
For more details get the DevOps for Web Development book.
It is also available at: