This is an interesting portrait of container-based production stacks, but I'm sure most companies aren't using containers.
This also doesn't mention anything about the application you're serving: HTTP servers, databases; nor does it mention the vehicle you use to push changes to your application (source control? ssh to host? ssh to each guest container, good heavens?), control distribution upgrades (how would you upgrade your kernel? how would you upgrade apache?), and so on.
What do other kinds of stacks that aren't on the "Container Bandwagon" look like? Just "ordinary" provisioning of virtual machines?
With so many problems, I don't think "Container" can be considered as equivalent to "Modern" quite yet.
I'm no expert, but I would imagine environments without containers probably use some sort of provisioning software like Chef or Ansible. If your application is big enough, you cannot manually deploy to each one as you described.
This article seems more like a container-centric description since there is no mention of build servers, applications, databases, etc.
Very true this is container based and is very much in the style of what I experienced over 10 years at Google. I put a disclaimer in the post to that.
I was also considering using the term "cloud native" over "modern" but didn't want to bring definition of that term into the discussion.
My bar for modern is that it should be self healing -- hardware/VMs should fail and the system should be able to recover without missing a beat. That requires a level of management and dynamism that is hard to get without containers. (Burning AMIs w/ autoscaling groups is a good alternative).
Comments
This is an interesting portrait of container-based production stacks, but I'm sure most companies aren't using containers.
This also doesn't mention anything about the application you're serving: HTTP servers, databases; nor does it mention the vehicle you use to push changes to your application (source control? ssh to host? ssh to each guest container, good heavens?), control distribution upgrades (how would you upgrade your kernel? how would you upgrade apache?), and so on.
What do other kinds of stacks that aren't on the "Container Bandwagon" look like? Just "ordinary" provisioning of virtual machines?
With so many problems, I don't think "Container" can be considered as equivalent to "Modern" quite yet.
I'm no expert, but I would imagine environments without containers probably use some sort of provisioning software like Chef or Ansible. If your application is big enough, you cannot manually deploy to each one as you described.
This article seems more like a container-centric description since there is no mention of build servers, applications, databases, etc.
Exactly. It would be really fun to explore those facets of a production pipeline.
I'm sure that's been written before, but I can't think of anything off the top of my head...
Very true this is container based and is very much in the style of what I experienced over 10 years at Google. I put a disclaimer in the post to that.
I was also considering using the term "cloud native" over "modern" but didn't want to bring definition of that term into the discussion.
My bar for modern is that it should be self healing -- hardware/VMs should fail and the system should be able to recover without missing a beat. That requires a level of management and dynamism that is hard to get without containers. (Burning AMIs w/ autoscaling groups is a good alternative).