Many organizations have large and monolithic business applications that can be hard to maintain and update. Given that the pressure to be able to adapt and change an organization is probably bigger today than it ever was, patterns and practices on how to modernize these applications become strategically important. One such pattern is the “Strangler Pattern,” which calls for strategically replacing dependencies and implementation bits of the monolith over time. A popular way of doing this is to move dependencies to APIs, and then to change the underlying implementation when it becomes necessary. Using this approach, parts of the monolith can still be used while other parts can be replaced, meaning that this approach avoids a risky “Big Bang”. Instead, this approach favors a more incremental and tactical way of modernizing monolithic applications.