Notes from production: Medusa.js, marketplaces, e-commerce, Next.js and AI.
Two stores look the same, yet one costs ten times more. Real code, measurements, and load tests from the Artovnia marketplace show how a production Medusa.js architecture handles failures, payments, and traffic.
Share & Save drops a seller's commission from 18% to 13% when that seller brought the customer in. Here is how signed click attribution, per-seller commission adjustments, double-charge protection, and a full audit trail work in a Medusa.js v2 marketplace.
Rebuilding 3DPCC from a cost calculator into a production management system took a seven hour planned outage. Five of those hours went to data migration scripts and verifying their results, not to shipping code. Here is the plan, the window, and what I took from it.
How to translate GPSR, DSA, GDPR, BDO, and DAC7 obligations into a reasonable MVP, without designing infrastructure for millions of listings. A practical architectural overview for marketplace builders.
A marketplace layer can be added to an existing online store without replacing the underlying platform. Inventory synchronization across vendors is the most complex part of the integration. The store operator retains full control over orders and the customer experience.
Cache in a Medusa.js marketplace is a design problem about source of truth and invalidation. At Artovnia (Medusa.js) we solved Next.js issues: two-layer promotions cache, nested unstable_cache bypassing Data Cache, ISR storing skeleton-only HTML, recommendation fan-out, and broken splitChunks.
