The Evolution of Container Usage at Netflix
techblog.netflix.com
The Evolution of Container Usage at Netflix
1–10 of 160 posts
Re: The Evolution of Container Usage at Netflix
#2>The theme that underlies all these improvements is developer innovation velocity
I can't wait until this becomes buzzword de jour and startups start using it in their product descriptions. Then someone needs to start talking about products to "enable developer innovation acceleration" to outpace these crufty companies stuck at 25 kph.
Re: The Evolution of Container Usage at Netflix
#3They're killing performance (one of the main reasons to use containers) and adding a massive extra layer of management if they're running containers on EC2.
I suspect Netflix are too wedded to AWS (which is weird as Amazon is their biggest threat) but Triton or Red Shift (both of which actually isolate containers using SmartOS and SELinux respectively) make way more sense for other people who want to use the blazing fast IO speed of containers on bare metal.
Re: The Evolution of Container Usage at Netflix
#4I would've imagined Netflix had their own hardware, both compute and storage.
Re: The Evolution of Container Usage at Netflix
#5I would've imagined Netflix had their own hardware, both compute and storage.
adrian cockcroft, who now works for aws, is known for a lot of his very early forward thinking approach to distributed applications and was responsible for their cloud architecture. I highly recommend checking out his medium and twitter, he's a brilliant man.
Re: The Evolution of Container Usage at Netflix
#6They're killing performance (one of the main reasons to use containers) and adding a massive extra layer of management if they're running containers on EC2. I suspect Netflix are too wedded to AWS (which is weird as Amazon is their biggest threat) but Triton or Red Shift (both of which actually isolate containers using SmartOS and SELinux respectively) make way more sense for other people who want to use the blazing…
Or use something like GKE where the containers should be running directly on hardware, so you only have one layer.
Re: The Evolution of Container Usage at Netflix
#7They're killing performance (one of the main reasons to use containers) and adding a massive extra layer of management if they're running containers on EC2. I suspect Netflix are too wedded to AWS (which is weird as Amazon is their biggest threat) but Triton or Red Shift (both of which actually isolate containers using SmartOS and SELinux respectively) make way more sense for other people who want to use the blazing…
Or use something like GKE where the containers should be running directly on hardware, so you only have one layer.
"Bare-metal" means running directly on hardware. But yes, GKE would also join Triton and Red Shift (provided it has similar container isolation capabilities).
Re: The Evolution of Container Usage at Netflix
#8I would've imagined Netflix had their own hardware, both compute and storage.
I've heard they're looking at 'architecture in a box' solutions, which would allow them to abstract designs from specific cloud providers and perform cloud arbitrage; eg, if Cloud Provider X can run the app at 14c/hour, and Cloud Provider Y can run the app at 22c/hour, then they can just deploy the entire architecture on Cloud Provider Y.
Re: The Evolution of Container Usage at Netflix
#9I would've imagined Netflix had their own hardware, both compute and storage.
They were fairly early and fairly vocal proponents of moving to cloud based systems. I haven't looked in awhile but last I checked all but their CDN was running on AWS.
Re: The Evolution of Container Usage at Netflix
#10I would've imagined Netflix had their own hardware, both compute and storage.
They were fairly early and fairly vocal proponents of moving to cloud based systems. I haven't looked in awhile but last I checked all but their CDN was running on AWS.
I thought their CDN was FreeBSD machines and everything else was on AWS.