Medusa Database Migrations: Generating, Reviewing and Deploying Safely
Generated migrations are only as safe as your review of them. How Medusa migrations work, and the expand-and-contract pattern that keeps rolling deploys from failing.
Generated migrations are only as safe as your review of them. How Medusa migrations work, and the expand-and-contract pattern that keeps rolling deploys from failing.
Configuring the Stripe module, wiring Payment Elements into a Next.js checkout, and the webhook and 3D Secure details that decide whether payments reconcile.
Address, shipping, payment session, complete. The four stages of a Medusa checkout, the state machine underneath, and the failure modes that cost orders.
What a production Medusa deployment actually needs — process separation, Redis, migrations, health checks — and the four mistakes that cause the first outage.
Medusa loads code by convention. A directory-by-directory guide to what goes where, and the decision tree for placing any new piece of logic.
How Medusa's payment abstraction works, why running two providers is easier than you think, and the authorise-versus-capture decision that determines your refund story.
Cart persistence, the guest-to-customer merge, inventory races and optimistic UI. The cart problems that only appear in production, and how to avoid them.
The dashboard is a React app you can extend. Injecting widgets into existing pages, adding new routes, and the conventions that keep extensions from looking bolted on.
How Medusa's event bus works, when a subscriber is the right tool instead of a workflow step, and the retry semantics you need to design around.
When a module should become a plugin, how the package is structured, and what changes when your code has to run in someone else's application.
The SDK is thin on purpose. What it handles, how authentication differs between store and admin, and why the fields parameter is the difference between a fast storefront and a slow one.
Everything in Medusa is resolved from a container. What is registered, how scoping works per request, and how to avoid the two mistakes that cause leaks.