LinkedIn Professional Network  ·  View 21 of 30  ·  5 · Runtime

Media — Upload, Process, Deliver

Bytes go straight from the client to Ambry, are scanned and transcoded, and are served from the CDN.

Editable source SVG draw.io All views
Upload Composer web · mobile Media service issues signed URL Resumable upload chunked · direct Store Ambry originals · immutable Quarantine never served Process Malware scan Image resize renditions Video transcode HLS · adaptive Content classifier Publish MediaReady Kafka Post attaches media Deliver Media CDN Azure Front Door Viewer infected Media — Upload, Process, Deliver Application we own Interface / broker Data store Risk / gap Security / platform Queue / topic Person or role failure / alternate Bytes never pass through a Rest.li service: the client writes to storage on a signed URL. v 1.0 · owner Media Engineering · date 2026-09

Decisions

  • Upload URLs are signed and time-limited, uploads are chunked and resumable, and bytes never pass through a Rest.li service
  • Ambry stores immutable originals. Renditions are derived and can be regenerated
  • A malware scan and a classifier gate serving; the post shows a placeholder until MediaReady

Numbers

  • Ambry: open-sourced 2016, active-active across data centres
  • The CDN should serve over 95% of media bytes (assumed target)

Risks

  • Resumes are documents full of personal data. They are served only on authorised short-lived URLs, never through the public CDN
  • A viral surge backs up transcoding; new posts get priority in the queue
◀  Notifications — Generate, Decide, Deliver All views Deployment Topology  ▶
Solution Architecture v1.0 · LinkedIn's own stack in LinkedIn-run colos · Enterprise Architecture · 2026-0921-media-pipeline