Manufacturing Planning API
2026 · Capstone project (Backend Developer)
The problem
A capstone project: a tool for planning and tracking manufacturing work job orders, machine scheduling, operation plans with approvals, and PPIC production schedules, meant to be shown as Gantt charts. It needed a backend that could model that whole workflow and serve it to a frontend.
What I built
- I built the entire backend: a Go API (Gin + GORM) of around 40 endpoints across eight models — users, job orders, machines, operation plans and their approval flow, PPIC schedules, G-code files, and a token blacklist.
- Auth is JWT with bcrypt, and the token blacklist means logging out actually revokes a token instead of just dropping it on the client.
- I kept it in clean handler–service–repository layers, with auto-migration and support for both PostgreSQL and MySQL, plus a set of tests.
The stack
- Gin
- GORM
- JWT
The result
- The frontend didn't get finished, so there's no live app to show this is the backend on its own: the API, the data model, and the auth.
- It's the most complete backend I've designed end to end, and the first large one I built in Go.
screenshot 16:10placeholder - set media in /content
backend