Source: dzone.com
Best Practices for Java DeploymentsCategory: Software, container
The proper deployment of Java applications can be a cumbersome and tedious process and the risk of failure is never higher than it is the moment after deployment. Errors during/after deployment not only impact IT development and operations of the organization but also your customers.To reach an optimal deployment process many projects and DevOps managers and engineers have adopted best practices to improve the deployment process to mitigate deployment risks.
For Mavenized Java projects, you specify your application version as well as declare your dependency in a pom.xml file, specifying the source of your artifact repository and voila, your application (with its inter-dependencies are shared).
Should you ever find yourself in a position where a production deployment fails or your Java application introduces a (new) critical flaw/bug in your application, the best policy will be to rollback your application to a known working version of your application.
One of the biggest challenges in Application Lifecycle Management (ALM) is dealing with the tasks of application deployment, various tools allow us to do an automated deployment.
For Mavenized Java projects, you specify your application version as well as declare your dependency in a pom.xml file, specifying the source of your artifact repository and voila, your application (with its inter-dependencies are shared).
Should you ever find yourself in a position where a production deployment fails or your Java application introduces a (new) critical flaw/bug in your application, the best policy will be to rollback your application to a known working version of your application.
One of the biggest challenges in Application Lifecycle Management (ALM) is dealing with the tasks of application deployment, various tools allow us to do an automated deployment.
Related Articles
Community Partners
DevOps Careers