4 ms·

The real world is still very much using Docker. Infact a few companies I've interviewed with this year aren't even using any kind of container setup and they're

The real world is still very much using Docker. Infact a few companies I've interviewed with this year aren't even using any kind of container setup and they're doing just fine and making money. This kind of article just adds to the Jonesing-for-shiny-things mentality that really doesn't do the engineering world any favours.

feketegy 7y ago
Not even docker, mostly AWS or dedicated servers or even VPS... No small site needs kubernetes/docker orchestration and that's fine.
- deleted 7y ago
  [deleted]
- deleted 7y ago
  [deleted]
- zer0tonin 7y ago
  Docker isn't just for orchestration. I've used it in a very small company and even use it for personal project just because it provides me with an easy to set up and portable development environment.
  - GrumpyNl 7y ago
    For my small personal projects, xampp is sufficient.
- pluma 7y ago
  The problem with AWS etc is that you need external servers (i.e. no good if it needs to run on the local intranet). Also the cost of adding even a new VPS is much higher than spinning up another docker instance. I'm pretty sure a lot of companies use docker simply to ease deployment of internal apps.
- sakisv 7y ago
  Docker can also be useful to create reproducible deployments, especially for languages like python when your dependencies may change between `pip install`s Having said that, I agree 100% that for most small/medium sized companies kubernetes is an overkill which creates more problems than it solved.
metalrufflez 7y ago
Pretty much I worked for an e-commerce, leader of their market, that used no Containers for the past 3 years. CI produced agnostic packages, which were deployed with Ansible in any environment and auto-scalable using Golden AMIs, EBS Snapshots and AWS ASG. Almost the same concept, but way less complex. We contemplated moving to ECS/EKS to stay "current" and to make test/development environments easier to create, but in the end, with a small team, it would add an unnecessary burden and "re-invent" the wheel on something that was working fine for the time being.
- znpy 7y ago
  > CI produced agnostic packages, which were deployed with Ansible in any environment and auto-scalable using Golden AMIs, EBS Snapshots and AWS ASG. Almost the same concept, but way less complex. I like this, i wish more orgs would work like that. Kubernetes feels mostly like a very opaque layer to abstract the underlying cloud vendor... Yet the cloud vendors are managing to get their lock-in back into kubernetes.
- lifeisstillgood 7y ago
  I would be interested in hearing you expand on this if you don't mind :-)
- regularfry 7y ago
  I can't help but feel that the drive towards docker-style containerisation was fueled by nothing more than the fad for developing on OS X. If you've got an environment where the devs are working on the same OS as production, it becomes much easier to adopt OS packages (whatever flavour that is) as the deployment mechanism, and as a side benefit it becomes easier to set up the dev environment in the first place. I've done this with Debian, it worked great.
  - kortex 7y ago
    I work on exactly the same OS as production (ubuntu 18.04) and still need (not want) containers to do my job. One project uses ROS along with different detectors with incompatible dependencies. One takes forever to build from source, and it's way easier to ship around images by pulling from a repo than tranferring binaries and libs. And even if I didn't have those constraints, I'd still use containers in production because it just makes testing and deployment so much less of a headache.
bittermandel 7y ago
My previous employer is a major gaming/media company and they don't run Kubernetes and largely (almost completely) no containers either. Focus is on uptime and profitability and it has really paid off!
- panpanna 7y ago
  Care to explain what that means?

feketegy 7y ago

Not even docker, mostly AWS or dedicated servers or even VPS... No small site needs kubernetes/docker orchestration and that's fine.

deleted 7y ago
[deleted]
deleted 7y ago
[deleted]
zer0tonin 7y ago
Docker isn't just for orchestration. I've used it in a very small company and even use it for personal project just because it provides me with an easy to set up and portable development environment.
- GrumpyNl 7y ago
  For my small personal projects, xampp is sufficient.
pluma 7y ago
The problem with AWS etc is that you need external servers (i.e. no good if it needs to run on the local intranet). Also the cost of adding even a new VPS is much higher than spinning up another docker instance. I'm pretty sure a lot of companies use docker simply to ease deployment of internal apps.
sakisv 7y ago
Docker can also be useful to create reproducible deployments, especially for languages like python when your dependencies may change between `pip install`s Having said that, I agree 100% that for most small/medium sized companies kubernetes is an overkill which creates more problems than it solved.

metalrufflez 7y ago

Pretty much I worked for an e-commerce, leader of their market, that used no Containers for the past 3 years. CI produced agnostic packages, which were deployed with Ansible in any environment and auto-scalable using Golden AMIs, EBS Snapshots and AWS ASG. Almost the same concept, but way less complex. We contemplated moving to ECS/EKS to stay "current" and to make test/development environments easier to create, but in the end, with a small team, it would add an unnecessary burden and "re-invent" the wheel on something that was working fine for the time being.

znpy 7y ago
> CI produced agnostic packages, which were deployed with Ansible in any environment and auto-scalable using Golden AMIs, EBS Snapshots and AWS ASG. Almost the same concept, but way less complex. I like this, i wish more orgs would work like that. Kubernetes feels mostly like a very opaque layer to abstract the underlying cloud vendor... Yet the cloud vendors are managing to get their lock-in back into kubernetes.
lifeisstillgood 7y ago
I would be interested in hearing you expand on this if you don't mind :-)
regularfry 7y ago
I can't help but feel that the drive towards docker-style containerisation was fueled by nothing more than the fad for developing on OS X. If you've got an environment where the devs are working on the same OS as production, it becomes much easier to adopt OS packages (whatever flavour that is) as the deployment mechanism, and as a side benefit it becomes easier to set up the dev environment in the first place. I've done this with Debian, it worked great.
- kortex 7y ago
  I work on exactly the same OS as production (ubuntu 18.04) and still need (not want) containers to do my job. One project uses ROS along with different detectors with incompatible dependencies. One takes forever to build from source, and it's way easier to ship around images by pulling from a repo than tranferring binaries and libs. And even if I didn't have those constraints, I'd still use containers in production because it just makes testing and deployment so much less of a headache.

bittermandel 7y ago

My previous employer is a major gaming/media company and they don't run Kubernetes and largely (almost completely) no containers either. Focus is on uptime and profitability and it has really paid off!

panpanna 7y ago
Care to explain what that means?