Back to selected projects
Private repository · sanitized public case study

OpenReels

Evolving a production-oriented video platform into a more independently developable, contract-driven system without making delivery unsafe for a solo operator.

The engineering challenge

OpenReels combines interactive social features, private media, asynchronous work, and production delivery. Early service separation existed at the process level, but development workflows, data ownership, and failure behavior still carried hidden coupling.

My objective was to deepen those boundaries while preserving working production behavior: protected media access, controlled database evolution, and an immutable release path could not be treated as disposable implementation details.

My role

I own the product architecture, implementation, validation strategy, protected delivery model, operational documentation, and release workflow. The work spans frontend product behavior, backend services, data and messaging boundaries, CDN authorization, and CI/CD.

Architecture at a safe level

This overview deliberately omits credentials, internal addresses, deployment topology, and security-sensitive operating procedures.

Product surface

A Next.js and React interface backed by explicit server-side application boundaries.

Services and data

Bun services coordinate PostgreSQL-owned state, Redis-backed runtime concerns, and typed contracts.

Asynchronous workflows

RabbitMQ messaging supports durable background work with validation, retries, and failure visibility.

Protected media

Private object storage and a guarded CDN path keep media access scoped to authorised product flows.

Selected outcomes

  • Separated product meaning from transport details through typed contracts and application-owned boundaries.
  • Created deterministic local development paths that do not require production credentials or cloud services.
  • Added explicit health, recovery, and observability behavior around service and messaging failure modes.
  • Preserved protected media delivery while improving authorization and range-playback reliability.
  • Kept releases reviewable through immutable artifacts, blocking validation, and health-aware rollout checks.

Honest constraints

OpenReels remains a private monorepo operated by one developer. It intentionally balances modular boundaries against operational simplicity rather than claiming database-per-service independence. Some shared infrastructure and larger service entry points remain documented engineering debt. Those constraints are part of the design discussion, not hidden from it.

Interested in the engineering decisions behind this work? Connect through the portfolio contact form or LinkedIn.