Scaling Medusa: What Breaks First and How to Fix It
Traffic does not break Medusa — the database does, then the workers, then the catalog queries. The bottlenecks in the order you will meet them.
Traffic does not break Medusa — the database does, then the workers, then the catalog queries. The bottlenecks in the order you will meet them.
Platform fees are the visible cost and rarely the largest. A three-year model comparing hosted SaaS against self-hosted Medusa, including the lines people leave out.
Both are TypeScript, both are self-hosted, both are good. The differences are in the extension model, the API style, and how much structure you want imposed.
Magento's EAV model, configurable products and multi-store hierarchy do not map one-to-one onto anything. How to extract, translate and cut over without losing B2B logic.
Tax-inclusive versus tax-exclusive pricing, product overrides, and the point at which manual rates stop being viable and you buy an engine.
Why your shipping options are empty, how the fulfilment model actually fits together, and how to build a provider that talks to a real carrier.
UPI, netbanking, RuPay and the mandate rules that make Indian payments their own discipline. Integrating Razorpay with Medusa properly.
Adding PayPal alongside cards, wiring the JS SDK buttons into a Next.js checkout, and the dispute and webhook behaviour that differs from a card processor.
The provider interface method by method, a working implementation, and the idempotency and webhook details that separate a demo from something you can take money with.
Medusa handles currency and tax per region, not translation. How to layer language onto that — URL structure, product content, and the hreflang most stores get wrong.
Two credible open-source commerce platforms with opposite technical bets. Which one fits depends far more on your team than on the feature lists.
WooCommerce data lives in WordPress's generic post tables. Extracting it cleanly, mapping variable products, and deciding what to do with thirty plugins.