4 ms·

It's hard to believe anyone is still promoting Docker. Has anyone actually used it? If you haven't jumped on the bandwagon yet, don't do it. It's a sucker's g

by lbayes 5y ago

It's hard to believe anyone is still promoting Docker. Has anyone actually used it? If you haven't jumped on the bandwagon yet, don't do it. It's a sucker's game. I got sucked into the Docker hype some years ago and the demos worked well enough in isolation. I pushed it on a small team that didn't need it. One of the biggest regrets of my career. Docker may be useful if an application has enormous reach and needs Google scale, but very few apps do. 1) It is incredibly slow to build 2) It is slow to run 3) It is an unbelievable resource hog 4) It has an entirely new set of problems (file system, networking, etc.) that must be understood to get it working 5) Hard deploy time dependency on Docker's web app?! 6) If you do not believe me on the complexity, just observe how docker arguments always seem to turn into k8s (or other orchestration) arguments. It is hard to reason about, hard to deploy, hard to coordinate. K8s is a total disaster for a small team working on a small project. We lost many months by choosing these tools for a startup that didn't (yet) need them, and the ongoing, neverending pile of problems and distractions they generated was shocking. I still feel bad about it. The company could have run on a couple $400 machines under a desk for years, but instead spent tens of thousands on AWS services it didn't need. Of course, YMMV

proxysna 5y ago
> Docker may be useful if an application has enormous reach and needs Google scale, but very few apps do. > I got sucked into the Docker hype some years ago and the demos worked well enough in isolation. > I pushed it on a small team that didn't need it. One of the biggest regrets of my career. It sounds like (no offence) issues that containerization solved were missed and you had no dedicated operations/build-engineer guy on your team that could've explained/fixed these things for you and steer your infra in a right direction. > I still feel bad about it. The company could have run on a couple $400 machines under a desk for years, but instead spent tens of thousands on AWS services it didn't need. Does not sound like a docker issue. If you actually plan to run a money making business that your livelihood depends on, then running it under your desk is not something that you can reliably do even 10-15 years ago. AWS is a money hog with a lot of things that are a distraction for a small project and it is easy to assume that their products are necessary to run your app effectively, but most often it is not. There is plenty of cloud providers that are not as expensive, and are much easier to manage compared to AWS. > K8s is a total disaster for a small team working on a small project. This is truly a YMMV thing. in my experience managed k8s for a small team can be a godsend for infra management after some level of complexity is reached, while self-hosted bare-metal k8s can utterly decimate the team. But again YMMV. I am currently running several clusters of Nomad for different types of workloads each. CI, HPC, VM's, public facing services you name it. Containerization makes it all possible to run (mostly) single-handedly.

by lbayes 5y ago

proxysna 5y ago

> Docker may be useful if an application has enormous reach and needs Google scale, but very few apps do. > I got sucked into the Docker hype some years ago and the demos worked well enough in isolation. > I pushed it on a small team that didn't need it. One of the biggest regrets of my career. It sounds like (no offence) issues that containerization solved were missed and you had no dedicated operations/build-engineer guy on your team that could've explained/fixed these things for you and steer your infra in a right direction. > I still feel bad about it. The company could have run on a couple $400 machines under a desk for years, but instead spent tens of thousands on AWS services it didn't need. Does not sound like a docker issue. If you actually plan to run a money making business that your livelihood depends on, then running it under your desk is not something that you can reliably do even 10-15 years ago. AWS is a money hog with a lot of things that are a distraction for a small project and it is easy to assume that their products are necessary to run your app effectively, but most often it is not. There is plenty of cloud providers that are not as expensive, and are much easier to manage compared to AWS. > K8s is a total disaster for a small team working on a small project. This is truly a YMMV thing. in my experience managed k8s for a small team can be a godsend for infra management after some level of complexity is reached, while self-hosted bare-metal k8s can utterly decimate the team. But again YMMV. I am currently running several clusters of Nomad for different types of workloads each. CI, HPC, VM's, public facing services you name it. Containerization makes it all possible to run (mostly) single-handedly.