Cloud Native Transformation: Practical Patterns for Innovation

by Pini Reznik, Jamie Dobson, Michelle Gienow

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


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

Genres: Technical, Technology, Business, Nonfiction, Software

540 pages, Kindle Edition

Published December 5, 2019

Reviews

[Darrin Snider · Rating 4 out of 5]

Something for Everyone

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.

[Jason · Rating 3 out of 5]

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.