- Effective DevOps with AWS
- Yogesh Raheja Giuseppe Borgese Nathaniel Felsen
- 361字
- 2021-07-23 16:27:24
Automating deployment
As you now, it is easier to write software in small chunks and deploy the new chunks as soon as possible, to make sure that they are working. To get there, companies practicing DevOps rely on continuous integration and continuous deployment pipelines. Whenever a new chunk of code is ready, the continuous integration pipeline kicks off. Through an automated testing system, the new code is run through all of the relevant, available tests. If the new code shows no obvious regression, it is considered valid and can be merged to the main code base. At that point, without further involvement from the developer, a new version of the service (or application) that includes those new changes will be created and handed off to a system called a continuous deployment system. The continuous deployment system will take the new builds and automatically deploy them to the different environments that are available. Depending on the complexity of the deployment pipeline, this might include a staging environment, an integration environment, and sometimes, a pre-production environment. Ultimately, if everything goes as planned (without any manual intervention), this new build will get deployed to production.
One aspect about practicing continuous integration and continuous deployment that often gets misunderstood is that new features don't have to be accessible to users as soon as they are developed. In this paradigm, developers heavily rely on feature flagging and dark launches. Essentially, whenever you develop new code and want to hide it from the end users, you set a flag in your service configuration to describe who gets access to the new feature, and how. At the engineering level, by dark launching a new feature this way, you can send production traffic to the service, but hide it from the UI, to see the impact it has on your database or on performance, for example. At the product level, you can decide to enable the new feature for only a small percentage of your users, to see if the new feature is working correctly and if the users who have access to the new feature are more engaged than the control group, for example.
- 零起步輕松學單片機技術(第2版)
- 亮劍.NET:.NET深入體驗與實戰精要
- 大數據專業英語
- 輕松學Java
- MCSA Windows Server 2016 Certification Guide:Exam 70-741
- 電氣控制與PLC原理及應用(歐姆龍機型)
- Python文本分析
- 無人駕駛感知智能
- 基于人工免疫原理的檢測系統模型及其應用
- 自適應學習:人工智能時代的教育革命
- Hands-On Geospatial Analysis with R and QGIS
- 超好玩的Python少兒編程
- 智能座艙之車載機器人交互設計與開發
- Cloud Native Development Patterns and Best Practices
- Mastering Windows Group Policy