I get the sense that this person wrote a sarcastic, vaguely entertaining piece that drew lots of views. Hoping for lightning to strike twice, they did this again because who doesn't love traffic? That seems to be the entire motivation behind this post, from what I can tell.
There's just not a ton of substantiated content here. It's mostly really lousy anecdata like:
> Sadly, I am not aware of any serious companies than run on Ubuntu.
I am troubled by the direction of Docker and there are serious issues, some of which were raised in this post. However, whatever signal there is in this post is lost in a sea of noisy ranting.
My advice to anyone who doesn't already have strong opinions:
* Complement any reading that you do with your own research.
* Don't try to invent your own container orchestration system.
* If you aren't sure how to best do something, ask someone!
And for the love of everything holy:
* Don't run stateful systems on Docker if you can't handle failure or data loss!
Docker and orchestration systems like Kubernetes can be an excellent pairing. It's going to require research, a change in how you develop, build, test, and deploy systems, and a gradual building of operational experience. It will not be a quick process, and it's not for every org. But for some orgs and usage cases, it's an excellent way to go!
I'm not sure I've personally been able to figure out if it was sarcasm or willful ignorance, but yeah, this article annoyed the pants off me just as much as the first in the series. The fact that it's now worked twice to hit the front page is also a little unsettling, because apparently one of the best ways to reach people on HN now is to just post a bunch of misinformed FUD (with !!Attitude!!) and jump on board the rocket ship!
There's just not a ton of substantiated content here. It's mostly really lousy anecdata like:
> Sadly, I am not aware of any serious companies than run on Ubuntu.
I am troubled by the direction of Docker and there are serious issues, some of which were raised in this post. However, whatever signal there is in this post is lost in a sea of noisy ranting.
My advice to anyone who doesn't already have strong opinions:
* Complement any reading that you do with your own research.
* Don't try to invent your own container orchestration system.
* If you aren't sure how to best do something, ask someone!
And for the love of everything holy:
* Don't run stateful systems on Docker if you can't handle failure or data loss!
Docker and orchestration systems like Kubernetes can be an excellent pairing. It's going to require research, a change in how you develop, build, test, and deploy systems, and a gradual building of operational experience. It will not be a quick process, and it's not for every org. But for some orgs and usage cases, it's an excellent way to go!