Strangling Your Data

A while ago, I wrote a post looking at different ways to modernize an application while retaining preexisting functionality.  One of these techniques is called the strangler patterns which gets its name from the strangler fig. The idea being: Create a shim for the current system. Record and/or replicate the data within the shim. As the new replacement services come …

Digital Transformation and Talent

Digital Transformation is a hot topic. Prior to the world changing due to the pandemic, it was integrating AI and machine learning assist with automating the risk calculations during policy underwriting or fraud detection when claims are filed. During the pandemic, the focus changed to the user experience for the agents, underwriters, adjusters, and even the customers facilitating remote work …

Anti-Corruption Pattern

The Anti-Corruption Pattern and Legacy Migration Strategies

Wrapping up the posts on Legacy Migration Strategies, this article will focus on the Anti-Corruption Pattern. The anti-corruption pattern describes some custom code to interface between a legacy application and a new target application. The reason why the pattern is called anti-corruption, is due to the corruptive nature of new development being forced to conform to a pre-defined legacy interface. …

Strangler Fig

The Strangler Pattern and Legacy Migration Strategies

Following up on my previous post on Legacy Migration Strategies, I will be talking about the strangler pattern. At its core, the approach is to take your original application, and replace it piece-by-piece by “strangling” it to death with each new component. The biggest reason for architecting with this approach in mind is to minimize the impact of the transition …