How we Serve Encrypted Video at 70+ Gbps Per Server With go and kTLS
We run a B2B platform for storing, processing, protecting, and delivering video over our own CDN, for customers from small startups to large enterprises. Under the hood that's high-load services, hundreds of thousands of requests per second, terabits of traffic, and a stack of home-grown components in Go, including our own CDN and DNS.
This story is about one hard problem inside that stack — TLS delivery: how our team took it from a stubborn ceiling to 70+ Gbps per 1U server, why HTTPS is more than a checkbox on a security list, and what we learned about kernel TLS, zero-copy, and a certificate default that quietly cost us seconds per handshake.
HTTPS isn't free
Kinescope (disclosure: I'm a co-founder of Kinescope. The Gbps are real, the bias is optional) is a SaaS product, so it runs over the internet, and like almost every modern service that means everything is...
Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE
