An open-source, composable commerce architecture

In this multi-part series article, we present Radixia Maca, our open-source solution for AI composable commerce.

Modern brands leverage e-commerce not just as a sales channel—it's a primary digital touchpoint that defines how customers experience, engage with, and remember you. It's where storytelling meets transaction, where brand identity is expressed through every click, search, and scroll. In this context, putting products online is no longer enough. To meet customer expectations, brands need flexible, intelligent, and cost-efficient commerce experiences that feel seamless across devices and moments. Whether you're launching a niche product line or managing global merchandise, the ability to move quickly, iterate frequently, and minimize operational overhead is essential. Today, composable and scalable e-commerce is no longer a nice-to-have—it's foundational to how modern brands build meaningful digital relationships.

As a case study to showcase our solution, we focus on ServerlessDays, a solution for merchandising—T-shirts, hats, keychains, and stickers—that wouldn't require a whole DevOps team to maintain.AWS Bedrock Agents, Commerce Layer, and Strapi CMS—all stitched together with AWS CDK, Lambda, and Fargate.

This isn't just a demo. It's a practical, production-grade reference implementation for composable commerce done right. It demonstrates how to create an intelligent, API-first e-commerce experience that serves as a blueprint for any team seeking to modernize digital commerce with minimal operational overhead and maximum scalability.

Why does this matter? Because too many e-commerce implementations are monolithic, fragile, or operationally burdensome. With this architecture, a modular, cloud-native stack.

In this multi-part article, we'll walk you through the whole architecture, from infrastructure-as-code to Bedrock-powered natural language product search. You'll see how we use:

• AWS Bedrock Agents and MCP servers to bring semantic search to commerce
• Commerce Layer to handle inventory, pricing, and order orchestration
• Strapi CMS for managing content and product metadata in a fully headless fashion
• A serverless infrastructure based on Lambda, Fargate, and CDK for elasticity and maintainability

Project Overview

The goal of this project is to create a modern, scalable, and easy-to-maintain e-commerce platform for selling ServerlessDay merchandise. The solution will leverage serverless technologies to minimize operational overhead and provide a flexible, cost-effective architecture. Key features of our implementation include:

1. Semantic Product Search: Using AWS Bedrock Agents to enable natural language search capabilities
2. Headless CMS: Using Strapi for content management
3. E-commerce API: Using Commerce Layer for product, inventory, and order management
4. Serverless Architecture: Using AWS Lambda and Fargate for compute resources
5. Infrastructure as Code: Using AWS CDK for infrastructure provisioning

Architecture Overview

Our serverless e-commerce architecture consists of several key components:

Frontend Layer

• Static Website: Hosted on Amazon S3 and distributed via CloudFront
• User Interface: Responsive design for both desktop and mobile devices

API Layer

• API Gateway: Exposes REST APIs for the frontend
• Lambda Functions: Process API requests and implement business logic
• Bedrock Agents: Provide semantic search capabilities

Content Management Layer

• Strapi CMS: Manages product content, descriptions, and images
• Fargate Service: Hosts the Strapi CMS application
• S3 Storage: Stores media files uploaded to Strapi

E-commerce Layer

• Commerce Layer: Manages product catalog, inventory, prices, and orders
• Integration Lambda: Synchronizes data between Strapi and Commerce Layer
• Order Processing Lambda: Handles order creation and fulfillment

Data Storage Layer

• DynamoDB: Stores product, order, and inventory data
• Amazon RDS: Database for Strapi CMS
• S3 Buckets: Store static assets and media files

Infrastructure Layer

• AWS CDK: Defines and provisions all infrastructure resources
• CloudWatch: Monitors application performance and logs
• IAM: Manages security and access control

Here's a visual representation of our architecture: