Skip to content
CodeNest

~/work/media-content-platforms

A Digital Asset Management platform, built end to end

A product that needed to store, organise and serve large volumes of media — with fast on-demand rendering and flexible metadata search, without re-processing everything up front. Built end to end, from API to deployment.

Industry
Media & content platform
Role
Full build
Services
Product development · Backend development · DevOps
Abstract illustration of a grid of image, video and document tiles, one being rendered

Challenge

The product needed to store, organise and serve large volumes of media assets. Users expected fast, on-demand rendering of thumbnails and derivatives, and flexible search across metadata — without the cost of re-processing every asset up front.

Approach

  • On-demand rendering with two paths. Built a Go (Gin) service that generates thumbnails and derivatives when they are first requested: a synchronous path for light media, and an asynchronous fallback for heavy jobs so requests never block on them.
  • Pluggable media processors. Processors are injected through dependency injection, so new asset types plug in without touching the core service.
  • Flexible, queryable metadata. Modelled metadata with PostgreSQL JSONB (via GORM), supporting filtering and sorting on arbitrary fields without a schema migration for every new attribute.
  • Containerised from day one. Packaged with Docker and deployed on Kubernetes, with assets in object storage.

Outcome

A complete platform — API, processing pipeline, metadata search and deployment — built end to end. Derivatives are produced only when needed, heavy jobs don’t block the request path, and new media types and metadata fields can be added without changes to the core.

Abstract illustration of radio signal rings connecting to distributed device nodes

Telecommunications & IoT

Scaling a real-time telecom charging & session platform

A mobile-core platform had to sustain millions of concurrent connectivity sessions, but under load the charging path became the throughput ceiling and nodes ran out of memory. We traced both to root cause, re-tuned the I/O-bound charging path and delivered a prioritised scaling strategy.

  • Go
  • NATS
  • Kafka
  • Redis / ElastiCache
Abstract illustration of ledger rows with a rising line chart

Billing & payment-grade data integrity

A billing event pipeline that never loses or double-charges

Core services published billing events to the broker in-process, coupling every write to broker availability and risking lost or duplicated events. We re-architected the pipeline around change-data capture and end-to-end idempotency.

  • Go
  • DynamoDB
  • DynamoDB Streams
  • AWS Lambda

~/next-step

Have something that needs to ship — and keep running?

Tell us what you are building. Within one business day you get a reply from a senior engineer, not a sales rep — with honest questions, a rough approach, and whether we are the right fit.

// NDA available before the first call.