4 ms·

> Up until now we’ve been deploying machines (the ops part of DevOps) separately from applications (the dev part). And we’ve even had two different teams admini

> Up until now we’ve been deploying machines (the ops part of DevOps) separately from applications (the dev part). And we’ve even had two different teams administering these parts of the application stack. Which is ludicrous because the application relies on the machine and the OS as well as the code, and thinking of them separately makes no sense. Containers unify the OS and the app within the developer’s toolkit. False. VM Blue/Green Phoenix Deployments were essentially "build VM for each release to production; spin up new VM; spin down old VM" which is essentially what Docker enables, except in container form....which you could have done with OpenVZ or any other containerization solution that has existed to date, even on AWS. > Up until now, we’ve been deploying heavy-weight virtualized servers in sizes that AWS provides. We couldn’t say “I want 0.1 of a CPU and 200MB of RAM”. We’ve been wasting both virtualization overhead as well as using more resources than our applications need. Containers can be deployed with much smaller requirements, and do a better job of sharing. As someone who runs & leases 128MB RAM VMs for various purposes...wut? You could have just as easily used OpenVZ to achieve this and literally everything else on your list: https://openvz.org/Main_Page https://openvz.org/Main_Page Or any other container-based solution. The only real thing you are saying with this article is: "We like the Docker ecosystem and we feel its better than all other solutions." Fair enough, but at least don't pretend Docker is the only way to solve these problems.

pbiggar 11y ago
This is a good example of what I was talking about at the start. Nothing that Docker does is completely new, and people were doing all these things before Docker. What Docker does is make them easier, pull them all into the same package, bring the ecosystem of tools around a single technology, and most of all: traction!
- vezzy-fnord 11y ago
  > Nothing that Docker does is completely new, and people were doing all these things before Docker. You're contradicting yourself, because in the same article you wrote: Into that world drops Docker: a new way of doing almost everything. It throws away old rules about operating systems, and deployment, and ops, and packaging, and firewalls, and PaaSes, and everything else. Then all the hype about the "future".
  - pbiggar 11y ago
    It's the same stuff, but it does it differently. So for example, instead of using AMIs to prebake images, it uses a weird AUFS layer. And it deploys using Dockerhub or by pushing images directly to hosts. And instead of using Mesos it has Swarm. And Kubernetes: that really is quite different to what we're doing, but not that different, conceptually, from what Heroku is.
    - fweespeech 11y ago
      Yeah, I took your post as vezzy-fnord did. But honestly, you have a very AWS-centric perception and the traction you talk about is really "Silicon Valley" specific. As long as you understand you are looking at a very, very narrow slice of the world when you use terms like that, sure, I can agree to that. For personal stuff, I use docker because its easy w/o all the tools I have at work. But that isn't the same thing as "unique and new".

pbiggar 11y ago

This is a good example of what I was talking about at the start. Nothing that Docker does is completely new, and people were doing all these things before Docker. What Docker does is make them easier, pull them all into the same package, bring the ecosystem of tools around a single technology, and most of all: traction!

vezzy-fnord 11y ago
> Nothing that Docker does is completely new, and people were doing all these things before Docker. You're contradicting yourself, because in the same article you wrote: Into that world drops Docker: a new way of doing almost everything. It throws away old rules about operating systems, and deployment, and ops, and packaging, and firewalls, and PaaSes, and everything else. Then all the hype about the "future".
- pbiggar 11y ago
  It's the same stuff, but it does it differently. So for example, instead of using AMIs to prebake images, it uses a weird AUFS layer. And it deploys using Dockerhub or by pushing images directly to hosts. And instead of using Mesos it has Swarm. And Kubernetes: that really is quite different to what we're doing, but not that different, conceptually, from what Heroku is.
  - fweespeech 11y ago
    Yeah, I took your post as vezzy-fnord did. But honestly, you have a very AWS-centric perception and the traction you talk about is really "Silicon Valley" specific. As long as you understand you are looking at a very, very narrow slice of the world when you use terms like that, sure, I can agree to that. For personal stuff, I use docker because its easy w/o all the tools I have at work. But that isn't the same thing as "unique and new".