<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Distributed-Processing on Sohil Ladhani Blog</title><link>https://sohilladhani.com/blog/tags/distributed-processing/</link><description>Recent content in Distributed-Processing on Sohil Ladhani Blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 16 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://sohilladhani.com/blog/tags/distributed-processing/index.xml" rel="self" type="application/rss+xml"/><item><title>Transcoding Pipelines: Processing Video at Scale</title><link>https://sohilladhani.com/blog/post/2026-03-16-transcoding-pipelines/</link><pubDate>Mon, 16 Mar 2026 00:00:00 +0000</pubDate><guid>https://sohilladhani.com/blog/post/2026-03-16-transcoding-pipelines/</guid><description>A user uploads a 4K video. Your system needs to produce: 4 resolution variants, 3 audio codec versions, thumbnails at 10-second intervals, and subtitle extraction. That&amp;rsquo;s not one job. That&amp;rsquo;s a directed acyclic graph of dependent tasks.
The Pipeline as a DAG Transcoding isn&amp;rsquo;t a linear process. Some steps depend on others. Some can run in parallel.
graph TD U["Upload: raw video"] --> V["Validate format"] V --> S["Split into segments"] S --> T1["</description></item></channel></rss>