Taytaotac
An e-commerce API built to be handed over.
- Year
- 2026
- Client
- Taytaotac
- Role
- Lead engineer
- Duration
- 5 months
Case study
The brief
An e-commerce platform built to be handed over — the client's own team would extend it after launch. That makes conventions and documentation part of the deliverable, not a nice-to-have.
The approach
NestJS with TypeORM on PostgreSQL, chosen precisely because it is opinionated: modules, providers and DTOs give the next developer one obvious place to put things. JWT auth with role-based access control, Swagger generated from the same decorators that validate requests, so the documentation cannot drift from the API.
Two Next.js frontends — a storefront and an admin — plus SQS for asynchronous work, Firebase for push, Sentry for errors, and Facebook OAuth for social login.
The harder parts
Discipline over speed. Every endpoint got a DTO and a Swagger annotation even when a plain object would have shipped faster, and the repo carries a dozen markdown files documenting the API surface with real curl examples. That is slower on day one and much faster on the day someone else has to add a feature without asking me anything.
Stack
- NestJS
- TypeScript
- TypeORM
- PostgreSQL
- Next.js
- Swagger
- AWS SQS
- Firebase
- Sentry
- Docker