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 book examines effective architecture, design, and cultural patterns to help you migrate to cloud native systems--whether you're moving from older architectures or creating new systems from scratch.
Cloud migration consultants Pini Reznik and Jamie Dobson draw patterns from the growing community of expert practitioners and enterprises that have successfully built cloud native systems. Technical managers and architects will learn what works and what doesn't when adopting cloud native--not just how this transition affects your technology but your company's culture as well.
You'll learn:
What cloud native means and why enterprises are so interested in it Common barriers and issues that have affected other companies Context-specific patterns for a successful cloud native adoption How to implement a safe, evolutionary cloud native approach How companies addressed root causes and misunderstandings that led to adoption problems
We read this as part of our " cloud team book club" at work. It's a very smart book. Some great examples and case studies, not technical at all, and a bit repetitive in that it annoyingly defines the same common concepts and patterns multiple times. Architects, analysts, engineers, developers all took something different away. In the end, it gave us foresight into where our cloud transformation would inevitably fail, a great reference to cite in the post-mortem documentation as to where and why things went wrong, and an insightful list of things to watch out for when interviewing for companies looking to move their operations to a cloud-based model.
The book focuses a lot on culture and process, as much as technology. The narrative used in the book doesn't necessarily support the examples, more real use cases would have helped the patterns instead.