- Foreword
- Preface
- Prologue: Evolve or Else
- 1. What Is Cloud Native?
- 2. The Human Challenge of Cloud Native
- I. Meet Our WealthGrid Team
- 3. What’s the Pattern? Architecture, Pattern Languages, and Design
- 4. Beyond Patterns: Behavior, Biases, and Managing Evolution
- II. First Attempt at Transformation–Cloud Native “Side Project”
- 5. Knowing Thyself: The Cloud Native Maturity Matrix Tool
- III. Second Attempt at Cloud Native
- 6. Tools for Understanding and Using Cloud Native Patterns
- 7. Patterns for Strategy and Risk Reduction
- Meet Steve
- Strategize, Then Delegate
- Pattern: Dynamic Strategy
- Pattern: Value Hierarchy
- Pattern: Business Case
- Pattern: Executive Commitment
- From Theory to Execution
- Pattern: Transformation Champion
- Pattern: Vision First
- Pattern: Objective Setting
- Pattern: Involve the Business
- Pattern: Periodic Checkups
- Pattern: Data-Driven Decision Making
- Pattern: Learning Loop
- Pattern: Learning Organization
- Pattern: Measure What Matters
- Pattern: Research Through Action
- Practical Patterns for Managing Any Kind of Risk
- Pattern: Gradually Raising the Stakes
- Pattern: No Regret Moves
- Pattern: Options and Hedges
- Pattern: Big Bet
- Pattern: Reduce Cost of Experimentation
- Pattern: Exit Strategy Over Vendor Lock-in
- Maintaining Strategic Momentum
- Pattern: Three Horizons
- Pattern: Reflective Breaks
- Pattern: Designated Strategist
- Ready for Next
- 8. Patterns for Organization and Culture
- Pattern: Core Team
- Pattern: Build-Run Teams (“Cloud Native DevOps”)
- Pattern: Platform Team
- Pattern: SRE Team
- Pattern: Remote Teams
- Pattern: Co-Located Teams
- Pattern: Communicate Through Tribes
- Pattern: Manage for Creativity
- Pattern: Manage for Proficiency
- Pattern: Strangle Monolithic Organizations
- Pattern: Gradual Onboarding
- Pattern: Design Thinking for Radical Innovation
- Pattern: Agile for New Development (Innovation Breaks)
- Pattern: Lean for Optimization
- Pattern: Internal Evangelism
- Pattern: Ongoing Education
- Pattern: Exploratory Experiments
- Pattern: Proof of Concept (PoC)
- Pattern: MVP Platform
- Pattern: Decide Closest to the Action
- Pattern: Productive Feedback
- Pattern: Psychological Safety
- Pattern: Personalized Relationships for Co-Creation
- Pattern: Blameless Inquiry
- Summary
- 9. Patterns for Development and Process
- Pattern: Open Source Internal Projects
- Pattern: Distributed Systems
- Pattern: Automated Testing
- Pattern: Continuous Integration
- Pattern: Reproducible Dev Environments
- Pattern: No Long Tests in CI/CD
- Pattern: Microservices Architecture
- Pattern: Communicate Through APIs
- Pattern: Reference Architecture
- Pattern: Architecture Drawing
- Pattern: Developer Starter Pack
- Pattern: Demo Applications
- Pattern: Secure System from the Start
- Pattern: Strangle Monolithic Application
- Pattern: Delayed Automation
- Pattern: Avoid Reinventing the Wheel
- Pattern: A/B Testing
- Pattern: Serverless
- Summary
- 10. Patterns for Infrastructure and Cloud
- Pattern: Private Cloud
- Pattern: Public Cloud
- Pattern: Automated Infrastructure
- Pattern: Self-Service
- Pattern: Dynamic Scheduling
- Pattern: Containerized Apps
- Pattern: Observability
- Pattern: Continuous Delivery
- Pattern: Continuous Deployment
- Pattern: Full Production Readiness
- Pattern: Risk-Reducing Deployment Strategies
- Pattern: Lift and Shift at the End
- Summary
- 11. Applying the Patterns: A Transformation Design Story, Part 1
- 12. Applying the Patterns: A Cloud Native Transformation Design, Part 2
- 13. Common Transformation Challenges
- Too-Early “Lift & Shift” Move
- Treating Cloud Native as Simply an Extension of Agile
- “Spiking” Cloud Native Transformation via Unbalanced Approach
- New System, Old Structure
- Wrong Order of Implementation
- Platform Not Ready for Production; Going to Production Anyway
- The Greenfield Myth, or, the “All or Nothing” Approach
- Lack of Platform Team
- Lack of Education and Onboarding Plan
- Summary
- 14. Building a Bank in a Year: Starling Bank Case Study
- 15. Welcome to the Jungle: Adidas Cloud Native Transformation Case Study
- Epilogue
- A. Library of Patterns (Thumbnail Reference Versions)
- Index
About the Authors
Pini Reznik is CTO and cofounder of Container Solutions, a consultancy that is helping companies to successfully adopt cloud native technologies and practices.
In the five years of existence of Container Solutions, they’ve participated and led dozens of cloud native transformations and collected extensive hands-on experience in both technical and organizational aspects of the transformation.
Jamie Dobson is cofounder and CEO of Container Solutions, a professional services consultancy specializing in cloud migration. A first encounter with a BBC computer and BASIC at the age of nine launched a lifelong passion for programming and software development. He eventually developed a matching passion for coaching and organizational strategy to help humans work effectively and beneficially with the technology that increasingly drives our lives.
Michelle Gienow is a web developer, JAMstack evangelist, and former journalist whose clients include The New Stack, Linux Foundation, New York Times, and Discovery Channel, among many. She is happiest when working amid the fascinating confluence of technology and writing, whether it’s JavaScript code or cloud native principles.
-
No Comment