News for hackers. Stuff that matters.

A comment on On Internal Engineering Practices at Amazon. Parent comment

Re:On Internal Engineering Practices at Amazon by scott_s on Wednesday March 27, 2019 @09:58AM (#19500822)
It's tempting to say that containers don't have any virtualization costs, but they often do for networking. For some applications, the addition of another networking driver doesn't matter. For others, it does.
[ Parent | on HN ]
Re:On Internal Engineering Practices at Amazon by m0zg on Wednesday March 27, 2019 @02:22PM (#19504202)
There is no "another networking driver" in containers. It's the same networking driver.
[ Parent | on HN ]
Re:On Internal Engineering Practices at Amazon by scott_s on Wednesday March 27, 2019 @11:41PM (#19509026)
For standard Docker container deployments, there is. See: https://docs.docker.com/network/
[ Parent | on HN ]
Re:On Internal Engineering Practices at Amazon by m0zg on Thursday March 28, 2019 @05:48AM (#19510664)
That's not a "driver" in the traditional sense, meaning it doesn't talk to the actual hardware directly. It's just a bridge or iptables.
[ Parent | on HN ]
Re:On Internal Engineering Practices at Amazon by scott_s on Thursday March 28, 2019 @03:34PM (#19515744)
shrug It's additional software in the networking stack, and it has a performance penalty. I think it's fair to call it a "virtualization cost," since you're paying for the container's networking abstraction.
[ Parent | on HN ]