Case study / Under construction
Goomer Menu API
The foundation of a menu API in TypeScript and Fastify, with a health check and architecture documentation.
Problem and user
Represent products, promotions and availability in a restaurant menu.
My role
Implementation of the technical foundation and documentation of its evolution.
Delivered scope
- Fastify server with a /health endpoint
- TypeScript configuration
- Data and flow diagrams
- Initial Prisma configuration
Constraints
- CRUD, promotions and persistence are not yet implemented on main.
- Vitest is configured, but the reviewed tree contains no tests.
Architecture and data flow
Fastify initializes the HTTP server. PostgreSQL and raw SQL are planned for queries; the Prisma configuration has no entities yet.
Decisions and trade-offs
Separate the runnable foundation from the product and promotion rules planned for subsequent stages.
Tests and validation
Public code and documentation reviewed on September 7, 2026. Running this project is outside the portfolio validation scope.
Current state
The foundation of a menu API in TypeScript and Fastify, with a health check and architecture documentation.
Known limitations
- CRUD, promotions and persistence are not yet implemented on main.
- Vitest is configured, but the reviewed tree contains no tests.
Next steps
- Expand test coverage and document upcoming deliveries.
Related training
- Santander Acceleration — Security Best Practices in Vibe Coding ↗
Documenting architecture (user-flow, data-flow, ERD) before writing code is the opposite of uncontrolled vibe coding — a discipline reinforced by this certificate.
- Backend — Final Project ↗
TypeScript, SQL and Prisma fundamentals related to the planned API architecture.
Stack
- TypeScript
- Fastify
- Node.js