That Strangler Fig Pattern is an architectural pattern in software development that describes the gradual replacement of a monolithic legacy system with new components without interrupting ongoing operations.
Named after the strangler fig that grows around an old tree over time and eventually replaces it, this pattern describes a method in which new software parts are gradually built up alongside an existing system. The new architecture „surrounds“ the monolith until it can be completely replaced.
The pattern is used in particular in modernisation projects for legacy systems, such as the migration of monolithic ERP or Accounting systems to modular microservices or cloud-based architectures. Companies use it to minimise risks and gradually introduce new technologies without jeopardising productive operations.
In contrast to a „big bang“ migration, in which an entire system is replaced at once, the Strangler Fig Pattern takes an evolutionary approach. It is therefore also in contrast to a „re-write“ (new development from scratch), which is often riskier and more expensive.
Example: A financial services provider uses an older accounting system that only runs locally. Instead of replacing it with a new cloud solution in one fell swoop, the invoicing module is first replaced with a new web service. This is followed by the dunning process, then incoming payment processing and so on. The new architecture gradually takes over the tasks until the monolith can be switched off.
ERP as standard - what does that mean?
Cash flow in companies explained
Work 4.0: Faster, further, higher or deceleration?
What are the advantages of a modern ERP solution?
What distinguishes the project management from the key user?
