Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Tounai34279dThey are not the same, and most of the time you will use Docker with k8s
Tounai34279d@matt-jd You should begin with Docker, learn how it works with both CLI and docker-compose (try to deploy a postgres image for example, and then, a Keycloak instance), and try to make your own image. Then, you will be able to understand the benefits of k8s.
I actually work for two companies, one is using docker and k8s, the other none of these. The first is a start-up, the second a relatively old company. Even if docker and k8s are both great tools, they are not the solution to everything.
AlmondSauce879179dMust admit I use docker because everyone else does, and not swayed from it.
Used K8s and AWS ECS for orchestration - the latter is simpler to set up and maintain, but doesn't have all the features of K8s, and obviously you're then tying yourself into AWS.
magicMirror683578d@matt-jd docker is build once, run everywhere solution. but... is also very usefull for a lot of things - for example, spinning up a temporary mongo instance, and doing some work with it. Then dispose the instance. Or playing around with redis. or elk. or a simple node app, with a postgres backend.
You can also use it to make code build faster, and cleaner. then pull the binary out of the image.
k8s is used to manage multiple docker hosts - learn what it is, but don't put too much effort into it.