How Loom Rebuilt Its Video Engine for Async Communication

Failed to add items

Sorry, we are unable to add the item because your shopping cart is already at capacity.

Add to basket failed.

Please try again later

Add to wishlist failed.

Please try again later

Remove from wishlist failed.

Please try again later

Adding to library failed

Please try again

Follow podcast failed

Unfollow podcast failed

How Loom Rebuilt Its Video Engine for Async Communication

Listen for free

View show details

In this episode of The CTO Podcast, Lucas and Luna dive into how Loom rebuilt its video recording and streaming engine to handle over 200 million videos per year while keeping latency under one second for uploads and playback. They explore the architectural shift from monolithic encoding to a microservices pipeline using WebAssembly for client-side transcoding, the trade-offs of moving from FFmpeg to a custom encoder, and how Loom cut infrastructure costs by 40 percent while improving reliability. The hosts also discuss the challenges of supporting asynchronous communication at scale, including real-time trimming and seamless playback across devices. If you're building a video platform or optimizing media delivery, this episode offers concrete lessons on balancing performance, cost, and user experience. Plus, Lucas shares how the team used Rust to reduce CPU usage for encoding by 60 percent. Tune in for a deep technical breakdown of one of the most popular async video tools in the workplace. #Loom #AsyncCommunication #VideoStreaming #WebAssembly #Rust #Transcoding #Microservices #FFmpeg #CostOptimization #Latency #Engineering #CTO #TechLeadership #Architecture #BusinessAndTechnology #FexingoBusiness #BusinessPodcast #MediaDelivery Keep every episode free: buymeacoffee.com/fexingo

No reviews yet