Project
A print-on-demand storefront whose design tool is a real layer-based editor in the browser — CMYK, PSD import, PDF out — on a commerce platform split into two dozen services.
What it is
AllPrintsCuts is a print-on-demand shop: pick a product — canvas prints, hoodies, mugs, photo books, flyers, roll labels, acrylic blocks — design it in the browser, and order it. The part that makes it more than a catalogue is the Design Studio, a full layer-based image editor that runs in the page rather than a template picker bolted onto a product photo. Behind the storefront the platform is built as a set of about two dozen services rather than one application, and the same catalogue is pushed out to Amazon, eBay and Etsy so the shop is one sales channel among several rather than the only one.
The Design Studio
This is the piece I would point at. It is a real editor: a layer stack with visibility, locking, opacity and blend modes, groups, a tool rail covering selection, crop, eyedropper, brush, eraser, fill, type and pen, rulers, and menus down to Filter and Select — and it keeps its own document format rather than flattening to an image between sessions. It is built on Fabric.js for the canvas, with Photoshop PSD files parsed client-side so a customer can bring artwork made somewhere else, and export through pdf-lib and jsPDF. The detail that gives away who it is for is the CMYK tab sitting beside the RGB colour picker: screens are RGB, presses are not, and a design tool that ignores that ships work which prints differently from what the customer approved.
Two dozen services, not one application
The backend is split by concern, mostly .NET with Python where the work is model-shaped: inventory, variations, pricing rules, cart rules, abandoned carts, gift cards, returns, shipping, tax, suppliers, multi-store, localisation, storage, CMS, SEO, report building, predictive analytics, a content generator, an AI agent, and an MCP service exposing tools to it. RabbitMQ carries the messaging between them. That is a lot of surface for a print shop, and the honest reason is that most of it is commerce machinery that any serious storefront needs and nobody sees — the interesting engineering is rarely the checkout button.
Selling in more than one place
A marketplace layer publishes the same product to eBay, Etsy and Amazon and keeps the listings in step: create a listing on one platform or on all of them at once, update it, delete it, and re-sync when the platform's copy and yours drift apart. Each marketplace is its own service because each has its own authentication, its own listing schema and its own opinion about what a product is; pretending they are interchangeable behind one adapter is how that kind of integration usually rots.
Running it
React 18 with Zustand and React Query on the front, Keycloak for sign-in so accounts are OIDC rather than a bespoke password table, and the whole thing on Kubernetes with per-service deployments, horizontal pod autoscalers, cert-manager certificates and a Jenkins pipeline that builds and applies them. It runs at allprintscuts.com.
Building a storefront?
Storefronts, design tools, marketplace integrations, and the commerce machinery nobody sees — tell me what you are building.