Composable Commerce

Composable DXP is a term widely used in resents years. In short it covers a composable architecture that creates the ultimate flexibility so you can pick-and-choose from a long list components. A way to pick and choose what components you want to be part of your Digital Experience Platform - DXP.

A number of questions arises fast when we typically discuss composable commerce:

So that means a lot more integrations between - so I need more developers and consultants?
With multiple components and systems - I now have to work in a different UIs and interfaces to get my work done?

The answer to the above questions is "Yes".

But that doesn't have to be like that, and it doesn't have to be a bad thing.

With larger "monolith" or "all-in-one" systems, you often pay for a lot of features that you never use, and those systems - due to their richness in features - has complex user interfaces.

The idea with a composable architecture is that you can combine component that fits your needs - as well as your wallet. If your demand changes - you can add a new component, or replaces an existing.

JAMSTACK & Next.js

"Jamstack is an architecture designed to make the web faster, more secure, and easier to scale".

At Alpha Solutions we encourage clients to utilize Jamstack architecture when possible. Reason being impressive user experiences and speed to the users and less cost in hosting to mention a few things. So why is Jamstack so fast?

The key here is "Pre-rendering" and CDN. Imagine that your content/pages got all created when you "publish" and then put on a CDN. When the user surf your website, it's actually directly on a CDN, and not hitting your servers or infrastructure at all. Now this is true for content-only websites, where there's no need for a log-in etc. For ecommerce it's obviously not possible to run it all off of a CDN - in that case interaction with various services is needed. Nevertheless this is an preferred approach, and it creates incredible experiences to the users.

Build like a MACH-star

The Pillars of Composable Commerce

Microservices

In the Composable Commerce approach, you build your architecture using microservices. A microservice can, for example, be a search function or a PIM system. Typically, you select the microservices that best meet your requirements—and it is easy to replace individual microservices if your needs change.

API first

In a composable setup, all microservices are connected via API's. The API's ensure to transfer data between the different microservices.

Cloud-native

One of the requirements for microservices in a composable setup is that they are cloud-based. This provides greater stability, as the platform scales automatically when needed. During peak periods with high traffic, additional bandwidth is allocated automatically to handle the load.

Headless

Traditionally, frontend and backend have been tightly coupled. With headless commerce, however, they are decoupled and connected via APIs. This offers a number of advantages. For example, frontend traffic does not impact the backend, and development can take place in the frontend and backend simultaneously. At the same time, page speed is improved, which has a positive effect on your performance.

Composable Solutions