Our modular suite of commerce software enables enterprises to gradually break down their legacy commerce platform with zero downtime. It also removes the need for enterprises to build core commerce functionality in-house as Amazon does.
In short, leveraging a modern commerce platform like Fabric lets you meet and exceed expectations from today’s consumers in less time, with fewer resources, at a lower cost. The biggest challenge you will face when modernizing your commerce stack is culture change, but Fabric can help you manage that as well. We offer high-touch support and additional services based on our leadership experience at Amazon, Staples, and eBay.
In the rest of this article, we will present some popular concepts and approaches for enterprises that modernize commerce.
Even legacy commerce platforms allow enterprises to separate the frontend presentation layer (i.e., head) from the backend commerce functionality. This is possible with platforms that expose APIs. For instance, instead of using legacy JSP pages from the legacy commerce platform Oracle ATG to deliver shopping experiences, you could call the platform’s REST services. You could make these API calls and pull data into a more modern frontend like Fabric XM.
Taking this approach would not fix your outdated, monolithic commerce architecture, but it would give you the ability to control frontend shopping experiences better. We work with large brands doing nearly a billion dollars in annual online sales that take this frontend-first approach. However, we also work with similar-sized brands that take a microservices-first approach by breaking down their monolithic backend.
Instead of initially separating your backend from the frontend, you can start modernizing your commerce stack by breaking down your legacy commerce platform with Fabric’s software and microservices. This is referred to as the strangler fig pattern. It’s a good approach for enterprises that are more satisfied with their frontend shopping experiences than their backend technology stack.
In our migration documentation, we present different approaches for breaking down monolithic commerce platforms used by enterprises. If you already know the benefits of microservices-based commerce, you might start by replacing a core commerce service like a product information manager with Fabric PIM. But if you want to ease your way into microservices-based commerce, you might start with a smaller service like cart or checkout. We have experience supporting each approach.
Last update: May 28, 2021