Everybody has to use JavaScript, Kubernetes, Docker, and a 500-person developer/infrastructure team. When in reality, 99.999% of websites could be made without JavaScript, hosted on a single VPS with SQLite.
There are legit reasons to use k8s and docker even on a small project. It ensures that your dependencies are isolated from those of the host OS. Gone are the days where you have to worry about multiple different services clashing because they all want to use the same ports, directories etc by default or different versions of the same service.
I’m also done being called at 2AM in the morning because the security team decided to automatically update all servers and forgot we were on the exemption list. Now our install is broken and nobody remembers what the original configuration was. So we spend 8 hours in a “war room” trying to unscramble our eggs. Docker makes everything infinitely more stable and it’s not that big of a deal to get running.
I don’t necessarily disagree. There are many ways to achieve the same or similar results. But docker seems to have become the popular option to the point where services are offering docker configurations out of the box. Meaning I have a standard, officially sanctioned way of doing what you described. Someone has already figured out how to properly containerize what to me is only a dependency and I can focus my efforts elsewhere. The option to get my hands dirty is still available, but it becomes a choice.
Yup, you can definitely take shortcuts that make development easier at the cost of maintenance being harder and more expensive. That’s exactly the problem I was describing.
There are legit reasons to use k8s and docker even on a small project. It ensures that your dependencies are isolated from those of the host OS. Gone are the days where you have to worry about multiple different services clashing because they all want to use the same ports, directories etc by default or different versions of the same service.
I’m also done being called at 2AM in the morning because the security team decided to automatically update all servers and forgot we were on the exemption list. Now our install is broken and nobody remembers what the original configuration was. So we spend 8 hours in a “war room” trying to unscramble our eggs. Docker makes everything infinitely more stable and it’s not that big of a deal to get running.
None of those things require Docker or Kubernetes…
I don’t necessarily disagree. There are many ways to achieve the same or similar results. But docker seems to have become the popular option to the point where services are offering docker configurations out of the box. Meaning I have a standard, officially sanctioned way of doing what you described. Someone has already figured out how to properly containerize what to me is only a dependency and I can focus my efforts elsewhere. The option to get my hands dirty is still available, but it becomes a choice.
Yup, you can definitely take shortcuts that make development easier at the cost of maintenance being harder and more expensive. That’s exactly the problem I was describing.