MERN Stack Development

Full-stack where Shopify is the wrong tool

Shopify is the right place to sell. It is the wrong place to run a healthcare platform, a role-based portal, or an API that other products depend on. That work is React on the client, Node.js and Express on the server, and a database with migrations — the MERN stack, used as an engineering choice rather than a slogan.

I am a MERN stack developer in Mohali, Punjab, and a Shopify engineer. The two sit next to each other because merchants often need a store and a system. The Shopify apps I build on Remix are cousins of this stack: React, Node, GraphQL, just pointed at the Admin API instead of a private schema.

Proof: Healthy-You healthcare platform

Healthy-You is a US healthcare product: health information, telehealth consultations, specialist matching and FSA/HSA-eligible services in one application. The hard part is the catalogue — 500+ health services in a hierarchical category system so a patient can move from a broad concern to a specific service without knowing clinical terminology.

Role-based access control separates what patients, advocates and practitioners can each see, which is what makes handling patient data under HIPAA tractable rather than a constant exception. FSA/HSA eligibility is surfaced on services before booking. Anyone who needs a human is routed to a patient advocate. Stack: React, Node.js, Express, Prisma, MySQL. The card lives on the projects page under MERN Stack.

React, Node, Prisma — and when Next.js is the front

The public site you are on is Next.js. Product work is often a React SPA or a Next app talking to an Express API. Prisma keeps the schema in git so hierarchical categories and role tables are migrations, not tribal knowledge. Redis sits in front of hot reads when the catalogue or the session store needs it — the same pattern I use on Shopify apps when Admin API rate limits would otherwise bite.

I am not a Mongo-or-nothing MERN developer. Document stores are right for some event logs and some product payloads. Patient records, RBAC and a 500-node service tree are relational. If a brief says "MERN" and means "React and Node, pick a database that fits", we will get on. If it means Mongo regardless of the domain, I will push back.

What I typically build

• React and Next.js front-ends with authenticated, role-aware views
• Node.js and Express APIs with Prisma over MySQL or MongoDB where documents fit
• RBAC, audit-friendly data access, and third-party integrations
• The same engineer who can then put a Shopify store or Remix app in front of it

If the product is commerce-first, start at hire a Shopify developer. If it is a platform with a store attached, say so in the brief — I would rather own the boundary than watch two vendors argue over it.