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 …

Don't let your cloud migration turn into a money pit

The Cost of Cloud Paradox

Over the holiday weekend, I stumbled upon a post from Andereessen Horowitz on the Cost of Cloud. The focus is mainly on software-based SaaS companies, but I would argue it applies to more traditional businesses thinking about their own cloud migration story. For SaaS companies, starting in the cloud makes perfect sense, it allows for very fast provisioning of resources …

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 …

Legacy Software Revelations

A long time ago, I posed a question on Twitter on what it means for software to be considered legacy. Since then, I’ve been correlating the few responses with my experience helping others with their migrations, prior client interviews, and the numerous articles I’ve seen ranging from Gartner to the smaller consultancies. There are other companies such as MuleSoft ESB …

Microservice Consolidation

As a developer and architect, it can be very easy to get caught up on the latest fads. Especially when looking at what’s on HackerNews or coming out of Silicon Valley. Microservices and Serverless functions are the rage in software development patterns. Who wouldn’t want a small simple component that is compartamentalized and allows for isolated changes? Components that do …

KubeCon US 2020 Summary

Last week concluded an event that was to originally take place in Boston prior to the pandemic. However, while still being at home, the feel was fairly similar to a conference as far as the number of talks. In fact, the talk portion of the day had a feel of a conference. Some were live streamed with more Q&A done …

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 …