The book provides a plethora of information on what 'Cloud Native' means and goes to describe how to get from monolith to cloud native in subsequent chapters. "Factor-in failure" seems to be the mantra to design and develop effective APIs employing redundancy and resiliency all the way.

Event-driven microservices, handling secrets through configuration, staying stateless to help in scaling out, comparing blue-green vs rolling upgrades vs parallel deployments to suit your use case, retries and circuit breaker to assist with ever-changing infrastructure are things you'll learn in part 2 of the book.

As mentioned by others, it's a little verbose - seems like the author introduced redundancy in the book as well - no pun intended. ( )