TechOps Examples
Hey — It's Govardhana MK 👋
Welcome to another technical edition.
Every Tuesday – You’ll receive a free edition with a byte-size use case, remote job opportunities, top news, tools, and articles.
Every Thursday and Saturday – You’ll receive a special edition with a deep dive use case, remote job opportunities and articles.
Most Kubernetes clusters waste over half their resources, and sharing a cluster between teams makes the problem worse.
Register for upcoming webinar on Sept 29 - hosted by Vikram Seshadri (Senior Evangelist, PerfectScale) and Hili Paryenti (Director of Product, Attribute) - and get tips on how to ensure an incorrect tenant memory doesn't become another tenant's outage.
IN TODAY'S EDITION
🧠 Use Case
How OTT Video Streaming Works on AWS
👀 Remote Jobs
Trust Wallet is hiring a Senior Platform Engineer
Remote Location: Worldwide
Canonical is hiring a Site Reliability Engineer
Remote Location: Worldwide
📚 Resources
If you’re not a subscriber, here’s what you missed last week.
To receive all the full articles and support TechOps Examples, consider subscribing:
🛠 TOOL OF THE DAY
kubectl-tree - kubectl plugin to browse Kubernetes object hierarchies as a tree.
🧠 USE CASE
How OTT Video Streaming Works on AWS
If you are using Netflix, Hotstar, or any OTT platform, the video you are watching right now almost certainly did not travel all the way from a data center in the US to your phone. It came from a server sitting much closer to you, one that already had a copy of that exact video file cached and ready to send. This is the entire reason OTT platforms can serve millions of concurrent viewers without every single request hammering one origin server, and the mechanism behind it is a Content Delivery Network, or CDN.
Content Delivery Network
A Content Delivery Network is a globally distributed system that helps deliver web content to users from the nearest possible location. It reduces load times, cuts latency, and improves performance.
At the heart of a CDN setup, there are two key components:
Origin:
This is where your main content lives. It could be a web server, a storage bucket like Amazon S3, or any backend system holding your files, APIs, images, or videos. The origin is the single source of truth for all your content.
Edge Locations:
These are geographically distributed servers that cache and serve content closer to the end users. When a user in London or Mumbai requests a file, instead of reaching all the way to the origin server in the US, the request is handled by the nearest edge location. The origin only gets hit when an edge location does not yet have the requested file cached, which is a small fraction of total traffic once a popular title has propagated across the network.
CloudFront
On AWS, this CDN function is provided by CloudFront, and understanding what actually happens at that edge location matters for anyone debugging why a video is buffering or why the wrong version of a file is being served.
A client, in this case an Apple TV running tvOS 17.3, sends a request for /videos/devops.mp4 with a query string specifying quality=1080p, along with request headers including User-Agent, Host, and Accept-Encoding. This request lands at a CloudFront edge location, which first checks its local cache. If the content is not already cached, the edge location forwards the request to the origin, carrying both the query string and the request headers along with it, and the origin, backed by an S3 bucket and a database server, returns the requested video.
The quality=1080p query string in this request matters more than it looks. If CloudFront's cache behavior is not configured to treat different query string values as distinct cache keys, a request for 1080p and a request for 480p can end up serving the same cached response to both viewers, since CloudFront by default may ignore query strings entirely unless told otherwise. This is a common source of OTT playback bugs where a user requests a specific quality and receives a completely different one, not because the origin sent the wrong file, but because the edge cache served a stale, mismatched entry.
Similarly, the User-Agent header shown here, identifying an Apple TV, is relevant when an origin serves device-specific manifests or bitrate ladders. If CloudFront's cache policy does not include User-Agent as part of the cache key, an Apple TV's request could be served a cached response originally generated for a different device type, leading to playback issues specific to that platform.
I hope this simplified the understanding behind OTT platforms functioning on AWS.
Kubernetes Multitenancy is the most adopted tech that is seeing a great rise in the market. We are bringing this hands-on workshop to help you experience and learn Kubernetes Multitenancy handling practically.
🔴 Get my DevOps & Kubernetes ebooks! (free for Premium Club and Personal Tier newsletter subscribers)
Looking to promote your company, product, service, or event to 50,000+ DevOps and Cloud Professionals? Let's work together.
