Modernise your retail systems with Patchworks iPaaS

At Patchworks we talk to retailers all the time about integrating a new piece of technology into their tech stack, and often it’s for one specific requirement.  In our experience, having a “data layer” or “integration layer” in your tech stack can actually provide a merchant with more flexibility to choose between systems, and more importantly a clear architecture and approach to integrations that is more “composable” as per the principals of our MACH Alliance certified software.  But how to get there? One of the proven ways is to adopt the “strangler fig” pattern.

The "strangler fig" design pattern, as popularised by Martin Fowler, is a gradual approach to replacing or modernising legacy systems without disrupting the existing operations. It’s named after the strangler fig tree, which slowly grows around an existing tree until the old tree no longer exists.

Here’s how a retailer can use the strangler fig design pattern along with the Patchworks integration platform as a service (iPaaS) to modernise their tech stack:

1. Identify the Legacy Architecture’s Components

• Inventory: Start by mapping out the legacy architecture, identifying key systems, components and workflows, such as order processing, inventory management, customer data handling, etc.
• Assess: Determine which parts of the system are most critical and where the modernisation efforts should start. Common candidates are those components that cause the most issues or are most costly to maintain.

2. Prioritise Modernisation Opportunities with immediate ROI

• Select a Target Area: Choose a specific function (e.g., order processing) to begin the modernisation process or start with a non-critical component to test the approach.  Look to deliver business benefits immediately either through saving costs or from increasing sales.
• Build or Integrate the New System: Buy the new platform or create a new microservice or component that performs the same function as the selected part of the legacy system. For example, modernise your EDI processing or integrate to a marketplace.

3. Integrate New Components Using Patchworks

• Connect New and Legacy Systems: Use the Patchworks iPaaS to create integrations between the new system and the existing legacy systems. Patchworks  manages the data synchronisation, transformation and routing, workflow automation, and API mappings between the old and new systems.

4. Route Traffic to the New System

• Gradual Transition: If possible start routing a portion of the data or specific data to the new system while still supporting the legacy system.  It might be that you integrate a new ERP for overseas orders that you will then use to replace the old ERP  so, for example, use Patchworks routing functionality to route based on the order country.
• Monitor and Iterate: Monitor the performance, reliability, and user feedback of the new component. Resolve any issues and gradually increase the load on the new system until it fully takes over.

5. Decommission Legacy Components

• Retire Legacy Code: Once the new system has fully replaced the functionality of a part of the legacy system, decommission that part of the legacy system.
• Repeat the Process: Continue the process with other components of the legacy system, slowly strangling it until the entire system is modernised.

6. Utilise Patchworks for Additional Capabilities

• Extend Integrations: As you add more new services or platforms, use Patchworks to continue connecting them, ensuring seamless data flow across your entire technology stack.  Quickly add blueprinted integrations to add new capabilities to your business.
• Centralised Control: Use Patchworks to maintain a centralised control over integrations, allowing you to easily manage and update your tech stack as it evolves.

7. Full Modernisation and Flexibility

• Complete the Transition: After all components have been replaced and the legacy system is fully decommissioned, the retailer will have a modern, flexible, and scalable tech stack.
• Future-proofing: With Patchworks in place, adding or replacing new services in the future becomes easier, allowing the retailer to stay agile and adapt to new technologies or market demands.

Benefits of the Strangler Fig pattern:

• Reduced Risk: By gradually transitioning to a modern system, the retailer can avoid the risks associated with a big-bang replacement.
• Continuous Operation: The business can continue running with minimal disruption since the legacy system remains operational during the transition.
• Flexibility: Patchworks provides a flexible integration layer that can adapt as the tech stack evolves, ensuring long-term agility.

In summary, we often see our agencies and customers using the "strangler fig" pattern with Patchworks to modernise their tech stack incrementally, reducing risks and ensuring continuity of operations. Patchworks facilitates seamless integration between the old and new systems, making the transition smoother and more manageable.