What is Deployment in DevOps?

In this post you will know the meaning of Deployment in DevOps. Deployment is updating your code on the servers. Servers can range from one to thousands. You need proper tools and strategies to deploy the code to server and refresh the site. To avoid breaking Live website, code is deployed to various stages. Testing-Staging-PreProd-Prod. Testing is where all the devs code are merged and deployed for internal testing. Staging is where client tests it as per the requirements. PreProd is same as Production. To make sure nothing breaks or there is no impact on any other feature.

Best Practice: code deployed to Production should never be rollback or reverted in master branch of git. That's why we have so many stages in deployment. You can automate this with CI/CD.. Learn more on CI/CD and also Docker. In Docker you deploy an image with os and code. It's a state of your application. You don't just deploy code folder but whole system at a stable state with everything working.

The main benefits for continuous deployment appear as a result of reducing lead time, the time elapsed between the identification of a requirement and its fulfillment, with two main consequences:

1. For each feature, after it is developed, an earlier return on investment, which lessen the need for large capital investments

2. Earlier evaluations from users on each new feature, which allows for A/B testing to establish which of several possible implementation is preferred by clients

CI and the two CDs can provide an outstanding environment for the entire DevOps team, while the benefits greatly outweigh the challenges, and high quality can be achieved even for very large capacity and scale systems, while delivering value and innovation very fast in same time.

Difference Between Continuous Delivery and Deployment in DevOps

In this post you will learn what is the difference between continuous Delivery and continuous deployment in DevOps. Continuity is the heart of the DevOps lifecycle and people often get confused between the terms Continuous Delivery and Continuous Deployment.

Continuous Delivery:

Continuous Delivery is a software development practice where you build software in such a way that the software can be released to the production at any time.

You achieve Continuous Delivery by continuously integrating the products built by the development team, running automated tests on those built products to detect problems and then push those files into production-like environments to ensure that the software works in production. Here Continuous Integration means continuously building and testing the application for every commit so that if application build or test failed , the developer is informed about it immediately.

 Software can be deployed to customers at any time with the "push of a button" (i.e. by running a deployment script).

Continuous Deployment:

Continuous deployment means that every change that you make, goes through the pipeline, and if it passes all the tests, it automatically gets deployed into production. So, with this approach, the quality of the software release completely depends on the quality of the test suite as everything is automated.

Software is automatically deployed to customers once it passes through the continuous integration system.