Movie.af / Re-Movie
A movie platform, rebuilt from the backend up.
- My role
- Backend engineering
- Focus
- Service boundaries · API design · TypeScript
Overview
A movie platform built on a microservices architecture, with independent services for catalog, users, and delivery communicating over well-defined APIs. My most complete backend system to date.
Problem
Rebuild a movie platform’s backend around three distinct responsibilities: catalog, users, and delivery.
What I worked on
- Backend engineering using NestJS and TypeScript.
- Work on independent services and the API contracts that connect them.
Technical approach & decisions
Separate the responsibilities
The rebuild had three distinct responsibilities: catalog, users, and delivery. The backend organises these as independent services, making the boundaries between product domains explicit.
Connect through APIs
Independent services still need to work together. Well-defined APIs connect the domains, so the contracts between services are part of the engineering work alongside each service’s implementation.
Work with a consistent stack
NestJS and TypeScript provide the foundation for the platform’s backend. This project brings together my work on APIs and service-oriented architecture.
Outcome
A movie platform organised into independent catalog, user, and delivery services connected through APIs.