- Implementing DevOps with Ansible 2
- Jonathan McAllister
- 182字
- 2021-07-02 19:02:54
Blue-green deployments
Blue-green is a development and deployment concept requiring two copies of the product, one called blue and other green, with one copy being the current release of the product. The other copy is in active development to become the next release as soon as it is deemed fit for production. Another benefit of using this development/deployment model is the ability to roll back to the previous release should the need arise. Blue-green deployments are vital to the concept of CI because, without the future release being developed in conjunction with the current release, hotfixes and fire/damage control become the norm, with innovation and overall focus suffering as a result.
Blue-green deployments specifically allow zero-downtime deployment to take place and for rollbacks to occur seamlessly (since the previous instance was never destroyed). Some very notable organizations have successfully implemented blue-green deployments. These companies include:
- Netflix
- Etsy
- Amazon
As a result of blue-green deployments, there have been some very notable successes within the DevOps world that have minimized the risk of deployment and increased the stability of the software systems.
- Design Principles for Process:driven Architectures Using Oracle BPM and SOA Suite 12c
- Software Testing using Visual Studio 2012
- MongoDB for Java Developers
- Cassandra Design Patterns(Second Edition)
- 深入淺出Android Jetpack
- 人臉識別原理及算法:動態人臉識別系統研究
- 深入淺出Serverless:技術原理與應用實踐
- Learning SciPy for Numerical and Scientific Computing(Second Edition)
- 0 bug:C/C++商用工程之道
- Advanced Express Web Application Development
- Quantum Computing and Blockchain in Business
- JavaScript+jQuery網頁特效設計任務驅動教程
- OpenCV with Python Blueprints
- 零基礎學C++(升級版)
- Python應用與實戰