All work
Product master APIs & dashboards
Centralized Master Data Management
Centralised product-master APIs and dashboards so one system owns the reference data other systems depend on.
- Role
- Backend and dashboard engineering at DCC Group.
- Stack
- NestJS · PostgreSQL · Prisma · Next.js · TypeScript
- Link
- No public URL

The problem
When product reference data is copied across systems, it drifts. A central master, exposed through well-defined APIs and managed from a dashboard, gives every consumer the same answer.
My role & responsibilities
- Product-master APIs built with NestJS.
- PostgreSQL data model accessed with Prisma where applicable.
- Next.js dashboards for managing master data.
Architecture
01
Master API
NestJS modules expose the product master with typed DTOs and validation.
02
Data layer
PostgreSQL via Prisma, with migrations tracked in version control.
03
Dashboard
Next.js interface for viewing and maintaining master records.
Engineering decisions
- One owner per piece of data; consumers read through the API instead of keeping their own copies.
- Typed schemas end to end, from database models to API contracts to the UI.
Challenges
- Agreeing a single shape for data that different teams describe differently.
- Changing the model safely while consumers depend on it.
What shipped
- Master data APIs and dashboards. Scope detail to be confirmed before further description.
Scope summarised conservatively; add verified detail in src/data/projects.ts.
Related service
Next case study
Quantum Cloud Gateway

