Like it or not the general consensus is the kubernetes, especially given the fact that it has backing from Google, has effectively won the container orchestration battle for the time being. That said, the bulk of people are going to promote that you should start learning kubernetes as soon as you feel comfortable with basic container orchestration concepts. speaking from personal experience it's a lot easier to be good at doctor swarm than it is to be good at kubernetes
that means they want to control the container orchestrator, which means they need some operational competency in their technology of choice. Many folks use swarm as their "first" production ready container orchestrator, because 1) they can heavily reuse any existing docker compose files (the yaml syntax has significant overlap) 2) swarm comes bundled as part of docker so the installation is quite painless 3) swarm is typically considered to be simpler than kubernetes 4) in my experience, companies that are just starting to get into container based deployments tend to come from a background where they control the infrastructure. The other two primary container orchestrators you're going to hear about, at least on this subreddit, are docker swarm and kubernetes. Naturally, there is a group of people that use it in production because it's a tool that they are familiar with and it works decently well as long as you only have basic requirements. Typically people say docker compose is not suited for production. Basically docker compose trades convenience for feature set. That simplicity means that it also lacks many features.
DOCKER LAMP STACK INSTALL
It is the container orchestrator of choice for local development for many folks, because it is super simple to install and run.
DOCKER LAMP STACK SOFTWARE
Docker is containerization software, it lets you define a container, define a container image, run a container.ĭocker is used in multiple parts of the software lifecycle (local development environments, as part of the CICD pipeline, and as part of a deployed system).ĭocker compose is a container orchestrator (turns on containers for you, monitors their life cycle, has some ability to react to changes in life cycle). You are mixing up docker compose with docker. I'm on mobile so there will be typos here: What's here will get you started on your own journey That would be useful for someone senior who already knows the basic concepts, but IMO is not useful for a beginner audience - it's too much information all at once. As some folks point out in comments, I could introduce 10 more technologies and be more precise with my terminology. Quick edit - This is getting a little attention, so some caveats - this is specifically written to target a novice / beginner reader, not an expert in docker.
0 kommentar(er)
