In this chapter, we discussed a risk migration strategy, known as the Strangler pattern, where we incrementally migrate to cloud-native following a roadmap of experimentation that is focused on adding value. We leverage bi-directional synchronization, so that features can continue to be used in the legacy system in tandem with the new cloud-native system. We empower self-sufficient, full-stack teams to define the migration roadmap, implement our cloud-native development practices, and establish the cloud-native foundational components. We discussed how our reactive, cloud-native architecture itself is designed to evolve by employing the Strangler pattern. I also left you with some final thoughts on how to welcome polyglot cloud and build a consistent team experience across multiple cloud providers.
For the next step, download the examples and give them a try. If you are...
