The document discusses software deployment principles and practices, outlining four key principles: repeatable builds, consistent environments, autonomous packages, and ease of doing/undoing releases. It provides details on each principle and how they can be achieved, such as through versioning of artifacts, baselining components together, and developing automated and documented processes.

What's hot

Viewers also liked

Similar to Software Deployment Principles & Practices

Recently uploaded

Software Deployment Principles & Practices

• 1.
  Software DeploymentPrinciples & Practices
• 2.
  Agenda Objective SoftwareDeployment Principles & Practices Repeatable Builds Consistent Environments Autonomous Packages Ease to-do/un-do Releases
• 3.
  Objective Basic introductionto Software Deployment Principles & Practices
• 4.
  What is SoftwareDeployment? Software Deployment is the art of deploying software artefacts (CI’s) produced as a result of build, on the target environment (Development, Staging, Production).
• 5.
  Principles of SoftwareDeployment One can consider 4 basic principles for software deployment, but not limited. Repeatable Builds Consistent Environments Autonomous Packages Ease to-do/un-do Releases
• 6.
  Repeatable Builds ATypical Application will undergo a simple “build-release-deploy” process with a defined build steps. One should have the provision of rebuilding the application exactly in the same way as it was built at the time of release, to achieve Repeatable builds One can Achieve Repeatable Builds, by ensuring Versioning of all software artefacts Versioning of all tools and its dependencies Baselining of all artefacts together Automated way of building Documented build process etc
• 7.
  Consistent Environments? AnEnvironment includes all the components needed to build and run the application. For a JAVA based application, on the server side the following components forms part of environment: Operating System (like solaris, HP-UX, AIX) System Libraries (like SH, openSSL) Services (like Apache, Oracle/Sybase) Run time Environments (like JDK, SDK) Application Servers (like WPS, Websphere) etc It is very important to keep all the above components consistent in all environments used for the build, release and deployment. Example: A developer might be doing development on windows based workstations, while the deployment has to be carried out on the UNIX based environment. In this case, consistency can be maintained at the Tool or Stack Level, by having the same JDK, SDK,app libraries etc.
• 8.
  Consistent Environments?...continued ConsistentEnvironment means in 2 ways: All Environments (Development, Staging) should use the same components (System, Software) to maintain consistency with the production environment (sometimes non-realistic, due to parallel dev/testing) Consistency with all developer environments (workstation etc) used for development, build and unit test. One can achieve a consistent Environment with the following: Version control of all components (server, workstation configurations etc) Centralizing the storage of the components & its downloads. Developing a strategy to run multiple versions of the components Automated/Scripted way of deploying components (server, application etc) Identifying and Documenting all application dependencies. Good Packaging Strategy Virtualization (VMWare, Virtual Server) Tracking Environment Changes with a good change management tool coupled with a robust process
• 9.
  Autonomous Packages? AutonomousPackages means the deployable package should exist independently. The more autonomous the deployable package is the more easier to deploy and maintain. Why software package autonomous is required? Running multiple instances of the packages independently All relative paths (configuration, logs etc) is relative to the package Application install/un-install, start/stop is independent to each package. Each package contains its own dependencies interms of version and libs required. : :
• 10.
  Easy to-do/un-do Releases?The most important part of the release is to know the environment. Doing a software release can be easy as installing a new version of the SW package into a single environment or installing multiple packages on multiple environments. How to ensure SW Releases can be easy to install/un-install/rollback? Knowing the Environment Understanding the dependencies Automated Release Strategy Testing Backup’s Documentation (release steps/notes, dependencies etc) : :
• 11.
  Thank You