Muutke küpsiste eelistusi

Cloud Native Transformation: Practical Patterns for Innovation [Pehme köide]

  • Formaat: Paperback / softback, 350 pages, kõrgus x laius: 232x178 mm
  • Ilmumisaeg: 31-Dec-2019
  • Kirjastus: O'Reilly Media
  • ISBN-10: 1492048909
  • ISBN-13: 9781492048909
Teised raamatud teemal:
  • Pehme köide
  • Hind: 75,81 €*
  • * hind on lõplik, st. muud allahindlused enam ei rakendu
  • Tavahind: 89,19 €
  • Säästad 15%
  • Raamatu kohalejõudmiseks kirjastusest kulub orienteeruvalt 2-4 nädalat
  • Kogus:
  • Lisa ostukorvi
  • Tasuta tarne
  • Tellimisaeg 2-4 nädalat
  • Lisa soovinimekirja
  • Formaat: Paperback / softback, 350 pages, kõrgus x laius: 232x178 mm
  • Ilmumisaeg: 31-Dec-2019
  • Kirjastus: O'Reilly Media
  • ISBN-10: 1492048909
  • ISBN-13: 9781492048909
Teised raamatud teemal:

In the past few years, going cloud native has been a big advantage for many companies. But it&;s a tough technique to get right, especially for enterprises with critical legacy systems. This practical hands-on guide examines effective architecture, design, and cultural patterns to help you transform your organization into a cloud native enterprise&;whether you&;re moving from older architectures or creating new systems from scratch.

By following Wealth Grid, a fictional company, you&;ll understand the challenges, dilemmas, and considerations that accompany a move to the cloud. Technical managers and architects will learn best practices for taking on a successful company-wide transformation.

Cloud migration consultants Pini Reznik, Jamie Dobson, and Michelle Gienow draw patterns from the growing community of expert practitioners and enterprises that have successfully built cloud native systems. You&;ll learn what works and what doesn&;t when adopting cloud native&;including how this transition affects not just your technology but also your organizational structure and processes.

You&;ll learn:

  • What cloud native means and why enterprises are so interested in it
  • Common barriers and pitfalls that have affected other companies (and how to avoid them)
  • Context-specific patterns for a successful cloud native transformation
  • How to implement a safe, evolutionary cloud native approach
  • How companies addressed root causes and misunderstandings that hindered their progress
  • Case studies from real-world companies that have succeeded with cloud native transformations
Foreword xi
Preface xiii
Prologue: Evolve or Else xxi
1 What Is Cloud Native?
1(14)
Cloud Native Is Not "The Cloud"
1(1)
A Cloud Native Primer
2(6)
How Do I Know Cloud Native When I See It?
3(1)
It's All About Services
4(4)
Fitting Everything Together
8(2)
What Could Possibly Go Wrong?
10(1)
(Distributed) Systems Shock
11(1)
Shocking Immaturity
12(1)
The Executive Summary
12(3)
2 The Human Challenge of Cloud Native
15(12)
Culture Vulture
16(1)
A (Brief) Field Guide to Organizational Culture
17(2)
"Right" Solutions, "Wrong" Culture
19(1)
The Culture Clash Conundrum
19(2)
Which Brings Us Back to Culture
21(2)
Interlude I Meet Our WealthGrid Team
23(4)
3 What's the Pattern? Architecture, Pattern Languages, and Design
27(16)
Patterns
28(2)
A Time for Design
30(1)
A Cloud Native Pattern Language
31(2)
Patterns in Context
32(1)
Cloud Native Context in the Real World
33(1)
Common Contexts
34(2)
Patterns, Pattern Languages, and Designs
36(7)
How Patterns Work
37(1)
What Makes a Pattern?
38(1)
How (Iba) Patterns Are Made
39(1)
Presentation
39(1)
Our Approach
40(3)
4 Beyond Patterns: Behavior, Biases, and Managing Evolution
43(20)
Conway's Law
44(1)
Cognitive Biases
45(1)
Why Biases Are Useful
46(1)
Biases, Patterns, and Behavior
47(2)
Nudges
49(2)
Common Biases and Nudges
51(6)
What to Watch For, and How to Overcome
57(2)
Interlude II First Attempt at Transformation-Cloud Native "Side Project"
59(4)
5 Knowing Thyself: The Cloud Native Maturity Matrix Tool
63(28)
Mirror, Mirror, on the Wall
64(1)
For Mature Audiences Only: The Maturity Matrix
64(1)
Staying in Sync
65(3)
Applying the Matrix
68(15)
Culture
68(1)
Product/Service Design
69(2)
Team
71(1)
Process
72(1)
Architecture
73(2)
Maintenance
75(2)
Delivery
77(2)
Provisioning
79(2)
Infrastructure
81(2)
Connecting the Dots
83(1)
The Axes, United
84(1)
Interlude III Second Attempt at Cloud Native
85(6)
6 Tools for Understanding and Using Cloud Native Patterns
91(18)
So Many (Deceptively Simple) Tools
93(2)
Tools to Take You the Rest of the Way
95(11)
Proficiency Versus Creativity
95(1)
Want Fries with That?
96(1)
Creativity, Proficiency, and Enterprise
97(4)
Three Horizons
101(2)
We Are the Champions?
103(3)
So What the Heck Happened at WealthGrid?
106(1)
Summary
107(2)
7 Patterns for Strategy and Risk Reduction
109(68)
Meet Steve
110(1)
Strategize, Then Delegate
111(2)
Pattern: Dynamic Strategy
113(3)
Pattern: Value Hierarchy
116(2)
Pattern: Business Case
118(3)
Pattern: Executive Commitment
121(2)
From Theory to Execution
123(1)
Pattern: Transformation Champion
124(3)
Pattern: Vision First
127(2)
Pattern: Objective Setting
129(3)
Pattern: Involve the Business
132(2)
Pattern: Periodic Checkups
134(2)
Pattern: Data-Driven Decision Making
136(2)
Pattern: Learning Loop
138(3)
Pattern: Learning Organization
141(3)
Pattern: Measure What Matters
144(2)
Pattern: Research Through Action
146(3)
Practical Patterns for Managing Any Kind of Risk
149(1)
Pattern: Gradually Raising the Stakes
150(3)
Pattern: No Regret Moves
153(3)
Pattern: Options and Hedges
156(2)
Pattern: Big Bet
158(4)
Pattern: Reduce Cost of Experimentation
162(3)
Pattern: Exit Strategy Over Vendor Lock-in
165(2)
Maintaining Strategic Momentum
167(1)
Pattern: Three Horizons
168(2)
Pattern: Reflective Breaks
170(3)
Pattern: Designated Strategist
173(2)
Ready for Next
175(2)
8 Patterns for Organization and Culture
177(68)
Pattern: Core Team
180(2)
Pattern: Build-Run Teams ("Cloud Native DevOps")
182(4)
Pattern: Platform Team
186(2)
Pattern: SRE Team
188(4)
Pattern: Remote Teams
192(2)
Pattern: Co-Located Teams
194(3)
Pattern: Communicate Through Tribes
197(3)
Pattern: Manage for Creativity
200(3)
Pattern: Manage for Proficiency
203(3)
Pattern: Strangle Monolithic Organizations
206(2)
Pattern: Gradual Onboarding
208(2)
Pattern: Design Thinking for Radical Innovation
210(2)
Pattern: Agile for New Development (Innovation Breaks)
212(3)
Pattern: Lean for Optimization
215(2)
Pattern: Internal Evangelism
217(3)
Pattern: Ongoing Education
220(2)
Pattern: Exploratory Experiments
222(3)
Pattern: Proof of Concept (PoC)
225(3)
Pattern: MVP Platform
228(2)
Pattern: Decide Closest to the Action
230(3)
Pattern: Productive Feedback
233(3)
Pattern: Psychological Safety
236(2)
Pattern: Personalized Relationships for Co-Creation
238(3)
Pattern: Blameless Inquiry
241(2)
Summary
243(2)
9 Patterns for Development and Process
245(46)
Pattern: Open Source Internal Projects
247(2)
Pattern: Distributed Systems
249(2)
Pattern: Automated Testing
251(2)
Pattern: Continuous Integration
253(2)
Pattern: Reproducible Dev Environments
255(3)
Pattern: No Long Tests in CI/CD
258(2)
Pattern: Microservices Architecture
260(2)
Pattern: Communicate Through APIs
262(2)
Pattern: Reference Architecture
264(3)
Pattern: Architecture Drawing
267(2)
Pattern: Developer Starter Pack
269(3)
Pattern: Demo Applications
272(2)
Pattern: Secure System from the Start
274(2)
Pattern: Strangle Monolithic Application
276(2)
Pattern: Delayed Automation
278(2)
Pattern: Avoid Reinventing the Wheel
280(3)
Pattern: A/B Testing
283(3)
Pattern: Serverless
286(2)
Summary
288(3)
10 Patterns for Infrastructure and Cloud
291(32)
Pattern: Private Cloud
293(2)
Pattern: Public Cloud
295(2)
Pattern: Automated Infrastructure
297(3)
Pattern: Self-Service
300(2)
Pattern: Dynamic Scheduling
302(3)
Pattern: Containerized Apps
305(2)
Pattern: Observability
307(2)
Pattern: Continuous Delivery
309(2)
Pattern: Continuous Deployment
311(2)
Pattern: Full Production Readiness
313(2)
Pattern: Risk-Reducing Deployment Strategies
315(3)
Pattern: Lift and Shift at the End
318(3)
Summary
321(2)
11 Applying the Patterns: A Transformation Design Story, Part 1
323(38)
Phase 1 Think
324(16)
Enter the Champion
325(3)
Ready to Commit
328(4)
Vision and Core Team
332(1)
Delegating Power
333(7)
Phase 2 Design
340(21)
Distributed Systems and Friends
344(4)
Exploratory Experiments
348(8)
Proof of Concept
356(5)
12 Applying the Patterns: A Cloud Native Transformation Design, Part 2
361(34)
Phase 3 Build
361(18)
Prepare for Onboarding
369(2)
Onboarding the Right Way, at the Right Time
371(8)
Phase 4 Run
379(13)
Strangle All the Old Things
382(4)
Keeping Creativity Alive
386(6)
The End?
392(3)
13 Common Transformation Challenges
395(26)
Too-Early "Lift & Shift" Move
396(3)
Treating Cloud Native as Simply an Extension of Agile
399(2)
"Spiking" Cloud Native Transformation via Unbalanced Approach
401(4)
New System, Old Structure
405(3)
Wrong Order of Implementation
408(2)
Platform Not Ready for Production; Going to Production Anyway
410(2)
The Greenfield Myth, or, the "All or Nothing" Approach
412(3)
Lack of Platform Team
415(2)
Lack of Education and Onboarding Plan
417(1)
Summary
418(3)
14 Building a Bank in a Year: Starling Bank Case Study
421(22)
Acing the Architecture
423(5)
Building the Apps
428(11)
No IT Department
429(2)
You Build It, You Run It
431(2)
Continuous Delivery
433(3)
Cloud Everything
436(3)
Resilient Architecture
439(2)
And, Really, That's It
441(2)
15 Welcome to the Jungle: Adidas Cloud Native Transformation Case Study
443(48)
Welcome to the Jungle
443(2)
A Playground for Kubernetes
445(2)
Day 2
447(10)
Day 2 Afternoon in Cloud City
457(4)
Epilogue
461(6)
A Library of Patterns (Thumbnail Reference Versions)
467(24)
Index 491
Michelle is a freelance web developer and 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.