A codified series of high level steps that we have seen help engineers reach the “aha” moment of understanding how their existing development workflow will need to change when they adopt cloud native technologies like Kubernetes.
4. @danielbryantuk
Workflow: Full Cycle Development
4
• App teams have full responsibility (and authority) for
delivering a service, and ultimately, value to users
• Increase agility by accelerating the feedback loop
• https://netflixtechblog.com/full-cycle-developers-at-netflix-a08c31f83249
5. The Kubernetes Migration Journey
5
Exploration
Organizational buy-in Cloud-native organization
We’re not actually moving faster
Let’s release our microservices as a monolith
7. Safety requires multiple strategies
7
Prevention
Mitigation
Detection
Response
Most common strategy (e.g., testing).
Mitigation, detection, and response are critical
strategies for cloud-native organizations when
the application is constant flux.
8. Safety Strategies
8
Prevention
Mitigation
Detection
Response
• Testing: integration tests, user acceptance tests, …
• High-fidelity replica environments for dev & test
• Engineering for resilience
• Progressive delivery: canary release, blue/green rollouts, …
• Observability
• Chaos engineering
• Fast dev / test loops
• Blameless postmortems
• Runbooks & game days
• Instant rollback & traceability
9. Safety needs to
be part of your
workflow.
9
Develop
Test
Deploy/
Release
Run
Progressive Delivery
Rollback
Observability
Chaos Engineering
Runbooks
Fast dev loop
Fast feedback
Realistic test
environments