DataSync Hub
A REST API and console for storing and sharing JSON data across applications and teams.
- Role
- Software Engineer
- Status
- shipped
Problem
Teams pass JSON configuration around in chat messages and gists, and nobody can say which copy is current. DataSync Hub puts it behind an API instead, so the record an application reads is the record a person edited.
Architecture
Read this diagram as text
- Next.js 15 client connects to REST API
- REST API connects to Prisma
- Prisma connects to PostgreSQL
Engineering decisions
The stack, reasoning not written up yet:
Next.js · TypeScript · Prisma · PostgreSQL · Tailwind CSS
The hard part
Storing arbitrary JSON in a relational database is a decision that looks free and is not. Everything can go in one schemaless column, and then nothing can be queried, migrated or validated — which is the state the gists and chat messages were already in. The document keeps its identity, owner and version in real columns and its free-form body as JSON, so the parts a team needs to search and the parts only the application understands are separated, and Prisma can migrate one without touching the other.
Result
A REST API over stored JSON documents with Prisma handling persistence and migrations, and a component-based console for reading and managing the structured data behind it.
Live and source
No public deployment — this one is not hosted anywhere a visitor can open. Happy to walk through it.