Continuous Delivery
 |
Description
Book Introduction
For successful deployment of software products
CI/CD Practical Guide
Continuous delivery is a core strategy for organizations that can flexibly respond to change even in complex systems.
This book begins with the concept and history of continuous delivery, systematically guiding you through the problems you inevitably encounter in practice and how to solve them.
It contains a concrete methodology that covers the entire development life cycle, from backlog segmentation in the planning phase, to safe incremental design during the development process, to testing and feedback strategies after deployment.
Covering a wide range of topics, from practical examples based on React, Spring Boot, and SQL to advanced topics like automated refactoring and A/B testing, it goes beyond simple technical explanations to provide practical solutions to real-world challenges.
Finally, we've included eight real-world examples of how global companies have transformed their technology culture by adopting continuous delivery.
Through this, you will be able to gain vivid insights and know-how that can be applied directly to practice.
CI/CD Practical Guide
Continuous delivery is a core strategy for organizations that can flexibly respond to change even in complex systems.
This book begins with the concept and history of continuous delivery, systematically guiding you through the problems you inevitably encounter in practice and how to solve them.
It contains a concrete methodology that covers the entire development life cycle, from backlog segmentation in the planning phase, to safe incremental design during the development process, to testing and feedback strategies after deployment.
Covering a wide range of topics, from practical examples based on React, Spring Boot, and SQL to advanced topics like automated refactoring and A/B testing, it goes beyond simple technical explanations to provide practical solutions to real-world challenges.
Finally, we've included eight real-world examples of how global companies have transformed their technology culture by adopting continuous delivery.
Through this, you will be able to gain vivid insights and know-how that can be applied directly to practice.
- You can preview some of the book's contents.
Preview
index
[PART 1 Continuous Delivery]
CHAPTER 01 Continuous Delivery
_1.1 Deployed once every few months or years
_1.2 Deployed once every few days
_1.3 Continuous Delivery
_1.4 Extreme Programming
_1.5 DevOps
_1.6 Continuous Integration
_1.7 Continuous Delivery
_1.8 Final Production Gate
_1.9 Implications
_1.10 Is continuous deployment dangerous?
_1.11 Organizing
CHAPTER 02 Advantages
_2.1 One Piece Flo and Rin Production
_2.2 DORA Metric
_2.3 Quality Shift Left
_2.4 Summary
CHAPTER 03 Shifting Your Mindset
_3.1 Defining and Applying Changes
_3.2 Hide work in progress
_3.3 Distributed Systems
_3.4 Contracts between production paths
_3.5 distribution is not a release
_3.6 End-to-End Delivery Lifecycle
_3.7 Summary
CHAPTER 04 MINIMUM REQUIREMENTS
_4.1 Autonomous Multifunctional Teams
_4.2 Stakeholder Trust
_4.3 Summary
CHAPTER 05 CHALLENGES
_5.1 Systems sensitive to distribution
_5.2 User Installed Software
_5.3 Regulated Industries
_5.4 Cognitive Load
_5.5 Summary
[PART 2 Before Development]
CHAPTER 06 Dividing Scheduled Work
_6.1 Horizontal Split vs. Vertical Split
_6.2 If you do continuous deployment
_6.3 Effective vertical segmentation
_6.4 Example: Grocery
_6.5 Summary
CHAPTER 07 PRODUCTION BUILDS
_7.1 Deployability Requirements
_7.2 Testability Requirements
_7.3 Observability Requirements
_7.4 Security Requirements
_7.5 Performance Requirements
_7.6 (A little more) complete user story template
_7.7 Example: Adding a CFR to the Grocery User Story
_7.8 Summary
[PART 3 Development Stage]
CHAPTER 08 Rebuilding the Platform Architecture
_8.1 User Story
_8.2 Grocery Application
_8.3 Organizing
CHAPTER 09 Refactoring Live Functions
_9.1 Things to do
_9.2 Product Identification System
_9.3 Current status
_9.4 Target State
_9.5 How to achieve your goals?
_9.6 Scaling implementation
_9.7 Organizing
CHAPTER 10 DATA AND DATA LOSS
_10.1 Things to do
_10.2 Current status
_10.3 Target State
_10.4 How to achieve your goals?
_10.5 Double-Write Implementation Strategy
_10.6 Double Read Implementation Strategy
_10.7 NoSQL
_10.8 Organizing
[PART 04 After Development]
CHAPTER 11 Testing in Production
_11.1 Why should I test in production?
_11.2 How to test in production?
_11.3 Story after staging
_11.4 Summary
CHAPTER 12 Release
_12.1 Antipattern: Big Bang Release
_12.2 Antipattern: Partial deployment: Releasing only a portion of the code
_12.3 Release Feature Toggle Application
_12.4 Canary Release
_12.5 A/B Testing
_12.6 Summary
[PART 05 Case Study]
CASE STUDY A AutoScout24
_A.1 The current situation of AutoScout24
_A.2 Introducing continuous distribution of AutoScout24
_A.3 Implementing continuous deployment of AutoScout24
CASE STUDY B Auto
_B.1 Otto's situation at the time
_B.2 Introducing continuous deployment of Otto
_B.3 Implementing Continuous Deployment of Auto
_B.4 References
CASE STUDY C N26
_C.1 N26's situation at the time
_C.2 Introducing continuous deployment of N26
_C.3 Implementing Continuous Delivery for N26
_C.4 References
CASE STUDY D Climate Partner
_D.1 Climate Partner's current situation
_D.2 Introducing Climate Partner's Continuous Distribution
_D.3 Implementing Continuous Distribution with Climate Partners
CASE STUDY E Mobility Operations
_E.1 Mobility Operations' current situation
_E.2 Introducing Continuous Delivery of Mobility Operations
_E.3 Implementing Continuous Delivery of Mobility Operations
CASE STUDY F Lea Group
_F.1 The situation of the Lea Group at the time
_F.2 Introducing continuous distribution of the Lea Group
_F.3 Implementing continuous deployment for the Lea Group
CASE STUDY G Maze
_G.1 Maze's situation at the time
_G.2 Introducing Maze's Continuous Delivery
_G.3 Implementing Continuous Delivery in Maze
CASE STUDY H Maze
_H.1 Travel Perk's current situation
_H.2 Introducing continuous distribution of TravelPerk
_H.3 Implementing continuous deployment of TravelPerk
CHAPTER 01 Continuous Delivery
_1.1 Deployed once every few months or years
_1.2 Deployed once every few days
_1.3 Continuous Delivery
_1.4 Extreme Programming
_1.5 DevOps
_1.6 Continuous Integration
_1.7 Continuous Delivery
_1.8 Final Production Gate
_1.9 Implications
_1.10 Is continuous deployment dangerous?
_1.11 Organizing
CHAPTER 02 Advantages
_2.1 One Piece Flo and Rin Production
_2.2 DORA Metric
_2.3 Quality Shift Left
_2.4 Summary
CHAPTER 03 Shifting Your Mindset
_3.1 Defining and Applying Changes
_3.2 Hide work in progress
_3.3 Distributed Systems
_3.4 Contracts between production paths
_3.5 distribution is not a release
_3.6 End-to-End Delivery Lifecycle
_3.7 Summary
CHAPTER 04 MINIMUM REQUIREMENTS
_4.1 Autonomous Multifunctional Teams
_4.2 Stakeholder Trust
_4.3 Summary
CHAPTER 05 CHALLENGES
_5.1 Systems sensitive to distribution
_5.2 User Installed Software
_5.3 Regulated Industries
_5.4 Cognitive Load
_5.5 Summary
[PART 2 Before Development]
CHAPTER 06 Dividing Scheduled Work
_6.1 Horizontal Split vs. Vertical Split
_6.2 If you do continuous deployment
_6.3 Effective vertical segmentation
_6.4 Example: Grocery
_6.5 Summary
CHAPTER 07 PRODUCTION BUILDS
_7.1 Deployability Requirements
_7.2 Testability Requirements
_7.3 Observability Requirements
_7.4 Security Requirements
_7.5 Performance Requirements
_7.6 (A little more) complete user story template
_7.7 Example: Adding a CFR to the Grocery User Story
_7.8 Summary
[PART 3 Development Stage]
CHAPTER 08 Rebuilding the Platform Architecture
_8.1 User Story
_8.2 Grocery Application
_8.3 Organizing
CHAPTER 09 Refactoring Live Functions
_9.1 Things to do
_9.2 Product Identification System
_9.3 Current status
_9.4 Target State
_9.5 How to achieve your goals?
_9.6 Scaling implementation
_9.7 Organizing
CHAPTER 10 DATA AND DATA LOSS
_10.1 Things to do
_10.2 Current status
_10.3 Target State
_10.4 How to achieve your goals?
_10.5 Double-Write Implementation Strategy
_10.6 Double Read Implementation Strategy
_10.7 NoSQL
_10.8 Organizing
[PART 04 After Development]
CHAPTER 11 Testing in Production
_11.1 Why should I test in production?
_11.2 How to test in production?
_11.3 Story after staging
_11.4 Summary
CHAPTER 12 Release
_12.1 Antipattern: Big Bang Release
_12.2 Antipattern: Partial deployment: Releasing only a portion of the code
_12.3 Release Feature Toggle Application
_12.4 Canary Release
_12.5 A/B Testing
_12.6 Summary
[PART 05 Case Study]
CASE STUDY A AutoScout24
_A.1 The current situation of AutoScout24
_A.2 Introducing continuous distribution of AutoScout24
_A.3 Implementing continuous deployment of AutoScout24
CASE STUDY B Auto
_B.1 Otto's situation at the time
_B.2 Introducing continuous deployment of Otto
_B.3 Implementing Continuous Deployment of Auto
_B.4 References
CASE STUDY C N26
_C.1 N26's situation at the time
_C.2 Introducing continuous deployment of N26
_C.3 Implementing Continuous Delivery for N26
_C.4 References
CASE STUDY D Climate Partner
_D.1 Climate Partner's current situation
_D.2 Introducing Climate Partner's Continuous Distribution
_D.3 Implementing Continuous Distribution with Climate Partners
CASE STUDY E Mobility Operations
_E.1 Mobility Operations' current situation
_E.2 Introducing Continuous Delivery of Mobility Operations
_E.3 Implementing Continuous Delivery of Mobility Operations
CASE STUDY F Lea Group
_F.1 The situation of the Lea Group at the time
_F.2 Introducing continuous distribution of the Lea Group
_F.3 Implementing continuous deployment for the Lea Group
CASE STUDY G Maze
_G.1 Maze's situation at the time
_G.2 Introducing Maze's Continuous Delivery
_G.3 Implementing Continuous Delivery in Maze
CASE STUDY H Maze
_H.1 Travel Perk's current situation
_H.2 Introducing continuous distribution of TravelPerk
_H.3 Implementing continuous deployment of TravelPerk
Detailed image
Publisher's Review
Building Trustworthy Software with Faster Feedback and Safer Releases
Distribution is no longer solely the responsibility of developers.
It's a core process that everyone—front-end, back-end, QA, and product managers—should be responsible for, and it's a crucial factor in determining organizational agility and product quality. Modern development cultures like the DORA metric, Lean, and DevOps are accelerating this transformation by blurring the lines between development and operations, shortening feedback loops, and more.
This book helps readers stand at the center of that flow.
This book provides a wide range of practical, hands-on skills and insights, covering everything from early development planning to post-deployment operations, including feature-level deployment, data migration, and A/B testing strategies.
Do you want to deliver software faster and more securely? Find the answers in this book.
Features of this book
● From theory to practice: Systematically guides you from the concept of continuous delivery to actual code-level implementation.
● Practical example code: Provides practical examples covering React (front-end), Spring Boot (back-end), and SQL (database).
● Safe change management: Provides concrete patterns for refactoring live functionality and migrating database schemas.
● Global Corporate Case Studies: In-depth analysis of how eight companies, including AutoScout24 and N26, adopted continuous delivery and transformed their technology culture.
● Improving development culture: Beyond technical practices, introducing a culture that enables organizations to respond to change and build trust.
Target audience
● I am familiar with continuous delivery, but I am not sure if it is the right practice for my team.
● People who are familiar with continuous delivery but not continuous deployment, so they always want to learn it properly.
● I joined a team that has implemented continuous delivery, and I want to know why and how to do it.
● If you've already decided to switch to continuous delivery, but want to know what happens when you remove the manual production gate
● I am planning a completely new product and would like to use this as an opportunity to apply continuous distribution, but since it is my first time, I am at a loss as to where and how to start.
Key Contents
● How to design your development plan with real-time production deployment in mind
● Patterns for refactoring functions in actual operation or changing the way data is stored
● How to test and release features in production environments with various feature toggles
● How to divide and distribute work considering visibility, performance, test automation, and security factors.
● A technique to prevent regression errors while gradually deploying the features you are working on to production.
Distribution is no longer solely the responsibility of developers.
It's a core process that everyone—front-end, back-end, QA, and product managers—should be responsible for, and it's a crucial factor in determining organizational agility and product quality. Modern development cultures like the DORA metric, Lean, and DevOps are accelerating this transformation by blurring the lines between development and operations, shortening feedback loops, and more.
This book helps readers stand at the center of that flow.
This book provides a wide range of practical, hands-on skills and insights, covering everything from early development planning to post-deployment operations, including feature-level deployment, data migration, and A/B testing strategies.
Do you want to deliver software faster and more securely? Find the answers in this book.
Features of this book
● From theory to practice: Systematically guides you from the concept of continuous delivery to actual code-level implementation.
● Practical example code: Provides practical examples covering React (front-end), Spring Boot (back-end), and SQL (database).
● Safe change management: Provides concrete patterns for refactoring live functionality and migrating database schemas.
● Global Corporate Case Studies: In-depth analysis of how eight companies, including AutoScout24 and N26, adopted continuous delivery and transformed their technology culture.
● Improving development culture: Beyond technical practices, introducing a culture that enables organizations to respond to change and build trust.
Target audience
● I am familiar with continuous delivery, but I am not sure if it is the right practice for my team.
● People who are familiar with continuous delivery but not continuous deployment, so they always want to learn it properly.
● I joined a team that has implemented continuous delivery, and I want to know why and how to do it.
● If you've already decided to switch to continuous delivery, but want to know what happens when you remove the manual production gate
● I am planning a completely new product and would like to use this as an opportunity to apply continuous distribution, but since it is my first time, I am at a loss as to where and how to start.
Key Contents
● How to design your development plan with real-time production deployment in mind
● Patterns for refactoring functions in actual operation or changing the way data is stored
● How to test and release features in production environments with various feature toggles
● How to divide and distribute work considering visibility, performance, test automation, and security factors.
● A technique to prevent regression errors while gradually deploying the features you are working on to production.
GOODS SPECIFICS
- Date of issue: July 28, 2025
- Page count, weight, size: 500 pages | 183*235*20mm
- ISBN13: 9791169214124
- ISBN10: 1169214126
You may also like
카테고리
korean
korean
![GQ KOREA Mark (Monthly): December [2025]](http://librairie.coreenne.fr/cdn/shop/files/8ef265dbbfbf186523ed75ba7319009d.jpg?v=1765340328&width=3840)
