Medishop

System Architecture

The Challenge

Healthcare commerce needs trustworthy product discovery and purchasing for customers, while operations need tight control over inventory, orders, and customers — two workloads that pull the product in different directions.

The Process

1. Step 01

   Connect the storefront to operations

   The Next.js storefront consumes the same Java/Spring Boot inventory and order APIs as the admin panel, so stock and order state are always consistent between customer and staff views.

2. Step 02

   Model inventory and orders properly

   MySQL schemas were designed for products, inventory, orders, and customers, with role-protected admin workflows built on top.

3. Step 03

   Manage media at scale with Cloudinary

   Product imagery and media run through Cloudinary, keeping large media out of the application bundle and the storefront fast.

4. Step 04

   Give admins Chart.js visibility

   The admin panel includes Chart.js dashboards for sales, inventory, and customer analytics so day-to-day decisions are data-backed.

The Outcome

An end-to-end medical e-commerce platform in production covering storefront, inventory, orders, customers, and administration.

Highlights

Ownership

End-to-end: storefront + admin panel + backend integration

Operations

Inventory, order, and customer management

Media

Cloudinary-managed product media

Reflection

Owning the storefront and admin panel end-to-end made integration decisions cheaper: one API change could be validated against both customer and operations flows in the same release.