Architecture
Evolve is a distributed system consinsting of a various number of components, depending on the implementation. It is intended to serve different compositions, depending on the use case that it implements. For example, a B2B use case most likely uses different components than a B2C case.
Through this model we are able to support any combination of SAAS services backing the domain services in Evolve.
Architecture overview
Through a layered architecture, Evolve is able to completely decoupled front-ends from the back-end, which in turn consists of several domain services that integrate different SAAS services and often also on-prem/custom services that are relevant to the use case.
GraphQL Federation is the key component that enables this.
AI integration through MCP
Beyond traditional storefronts, Evolve's GraphQL Federation layer also serves as the foundation for AI integrations. Through the Model Context Protocol (MCP), Evolve exposes its commerce capabilities as tools that AI assistants can discover and invoke. MCP servers sit alongside storefronts as clients of the GraphQL gateway, enabling conversational commerce, AI-powered customer support, and autonomous workflows without duplicating any business logic.
Architecture topics
🗃️ Core architecture
6 items
🗃️ Infrastructure
7 items
🗃️ Frontend
2 items
📄️ Payment architecture
How payment providers integrate with the checkout service and commercetools.
🗃️ Model Context Protocol (MCP)
5 items
📄️ B2B & B2C architecture
How Evolve runs B2C and B2B commerce from the same backend, letting you build sites that are B2C-only, B2B-only, or a combination of both.
🗃️ Cloud deployment
3 items
📄️ Design principles
The design principles behind Evolve's architecture and how they shape the platform.
📄️ MACH integrations
Evolve offers many integrations with a wide range of SAAS services. Evolve is
📄️ Background articles
Recommended background articles to read.