Strangler Pattern

Photo by Chris Chow both here and on today's Audio Podcast on #Soundcloud

Once again I find myself back at the #ChatGPT openAI API using it as a better "google" to quickly google the best results. Kind of like that famous "I'm feeling lucky" button. However, just now when I tested it on this topic, it came back with a website full -o- s/p/a/m. #justSayin

Today's issue started when I noticed Nicolas M. Chaillan 's post on something called the "strangler pattern" here on LinkedIn. Which led me to his video. As I commented, I have replaced numerous business software applications but never used this formal procedure. In fact, my memory banks were blank of the concept. By the way, Nic and I share a love of IT/IS and data processing adventures, him in the security world, and me mostly in business.

So, a quick trip to #ChatGPT "A.I. Powered" data banks...

SKI: In business, what is the concept known as "strangler pattern" for change?

ChatGPT: The "strangler pattern" is a software design pattern that involves gradually replacing a legacy system with a new system, while both systems are in use at the same time. This pattern is sometimes referred to as the "strangler fig" pattern because it is inspired by the way that a fig tree (also known as a strangler fig) grows by wrapping its roots and branches around a host tree, eventually strangling the host tree and taking its place.

The idea behind the strangler pattern is to allow an organization to gradually transition from an old system to a new system, without disrupting the business or requiring a complete overhaul of the existing system all at once. This can be especially useful in cases where the legacy system is large and complex, and it would be difficult or impossible to replace it all at once.

To implement the strangler pattern, the new system is built alongside the existing system, and the two systems are connected through a set of interfaces. As the new system is developed, it gradually takes over more and more of the functionality of the legacy system, until eventually the legacy system can be retired and the new system is handling all of the necessary tasks.

The strangler pattern can be an effective way to manage the process of change in an organization, particularly when it comes to updating or replacing legacy systems. It allows the organization to make the transition to a new system in a controlled and gradual manner, minimizing the risk of disruption and maximizing the chances of success.

__

So, thanks again Nic. It pays to have smart friends.

Have I convinced you to consider giving ChatGPT a try [or two; maybe three]?

#YouHaveNotBecauseYouAskNot

P.S. Check out our updated footer... below ↓↓↓

__

Jeff 'SKI' Kinsey is a Jonah's Jonah in Dr. Eli Goldratt's TOC (Theory of Constraints), author of Purple Curve Effect — SKI's Through on Command, and taught Computer Science for 10 years. U.S. Marine Corps Veteran w/ a Letter of Commendation for process improvement and spent 20+ years in full lifecycle software development including eCommerce soultions that have booked hundreds of millions of dollars in revenue. His 40+ years of computer and business consulting across America has created hundreds of jobs and career advancement. His first, best destiny is entrepreneur. Fifty years later the SKI Man is on his 22nd Startup: FastChargeEnergy? and yet he still finds time for clients, some going back over 30 years. Need a second opinion? Ask!