From the course: Microservices: Design Patterns
Join today to access over 24,500 courses taught by industry experts.
Strangler pattern
From the course: Microservices: Design Patterns
Strangler pattern
- Now that we have discussed some of the most common decomposition patterns, we need to talk for a bit about how to get there from a legacy system. So let's talk about the strangler pattern from a high level conceptual point of view. It really is a simple pattern as long as you can plan appropriately. The idea behind the pattern as a whole is you start with your monolith and then essentially carve your dependencies off of it. You shard your services off piece by piece into new microservice endpoints. Point the internal client to the new microservice, and eventually, deprecate the functionality out of your monolith once all of the dependencies are weaned off of it, and you've now strangled it. You can break your services off at the API layer first by building out the API and underlying service, and then moving the database behind it, assuming it's a data domain service. You can likewise start at the data store itself and move the domains out, and then traverse up the tree to business…
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.
