Deployability is the ease, speed, and reliability of deploying a tested component into production. In a fast-flow organization, changes may be deployed at least once per developer per day, making deployment friction an architectural concern. section 5.5
A deployable architecture supports deployments that:
- Run automatically and quickly after the deployment pipeline validates a change. section 5.5 section 5.7
- Avoid downtime and production impact while preserving service-level agreements. section 5.5.1
- Detect startup or performance failures and roll back automatically. section 5.5.1 section 5.7
Spring Boot deployment to Kubernetes
A deployment mechanism builds and publishes a container image, updates Kubernetes YAML to reference its version, and triggers a rolling update that replaces old service instances with new ones. The mechanism can be split between the deployment pipeline and the Kubernetes cluster. section 5.5
Deployability is influenced by component architecture. A multi-component design can support independent deployment, while microservices improve fast flow through independently owned services and separate deployment pipelines; these benefits require disciplined dependency management. section 5.7 section 7.4.1

