- Role
- Full-stack engineer
- Period
- 2023–present
- Register
- Full-stack
- Locus
- 06°10′S 106°49′E
A public knowledge and dataset portal for a government planning body: a catalogue service, a backend-for-frontend layer, and multiple front-ends over one contract.
01Context
Content and datasets lived across several services with divergent shapes. The portal needed one dependable contract every front-end could trust.
02Approach
- 01
Consolidated a fragmented microservice lineage toward a sync-ready model with stable IDs and merged bilingual content.
- 02
Introduced a backend-for-frontend so multiple apps consume one catalogue service through a single typed client.
- 03
Documented the contract as a rendered OpenAPI site, so the spec is the single source of truth.
03Outcome
A maintainable system whose data model and API contract are legible to every team that touches it.
04Stack
- Next.js
- OpenAPI
- BFF
- TypeScript
- PostgreSQL