• Dynatrace

Microsoft Azure - Application Insight (free and powerful)

Dynatrace was previous winner for stand alone.

• Cloud Provider Module
  
  
• Dynatrace
• CA APM (previously Wily Introscope)

Unified view and control of containers who should hook themselves up and configure to the larger group.

• etcd used by Kubernetes (started by Google)
• Swarm (Native Docker)
• ZooKeeper used by Mesosphere + Marathon (preferred by DC/OS)
• Chef (to a certain extent through infrastructure automation)
• Eureka (by Netflix) used by Spring Cloud but services must be stateless and network non-sticky
• HashiCorp Console
  
  

Comparison (to be made)

• Zero Footprint with Scripts
• Habitat

No point in running the hardware and base OS yourself. Instead use a provider that will take care of auto-scaling hardware, providing IP addresses, storage and a network infrastructure.

Bonus points for instituted caching and monitoring. ++ Bonus points for an proven CICD system.

Some of the Bonus items you can implement yourself and are documented higher in this stack.

At the moment (2016)

Microsoft Azure for ease of use.

• Microsoft Azure
• Amazon AWS
• Google Cloud Platform
• Rackspace

If you have lots of integration points, centralizing one place to configure those small differences suddenly becomes cost effective.

This is not actually service discovery (though having it helps immensely)

• Habitat (tackles applications provided you use it's packaging)
• Ansible

• Chef Kitchen

• saves application data apart from the application instance so data is still available for application <X + 1> when application <X> goes down

Depends on your specific messaging needs.

Will break this up later.

• Kafka
• RabbitMQ

• Building from Recipes
• Linking of Containers

• Docker

Often initiated by the CI/CD pipeline control to build the operating system, setup users, install software and apply configuration.

Configuration Management and Infrastructure as Code.

This includes SDN (Software Defined Networking) which is still a growing space as the what's available is still rudimentary.

Chef and Puppet are leading (2017) configuration management tools.

However, they don't solve (without fiddling) stateful applications requiring workflow deployment, ie upgrade of a database.

• Chef
• Puppet
• Docker (do for more than just the os and base?)
• Ansible
• SaltStack
• Terraform

Comparison

The big cloud providers provide true infrastructure as code to provision (build and manage) all your resources (virtual machines, network, ect...).

Often tightly paired and confused with with Configuration Management and CICD tools.

• Azure ARM (Azure Resource Manager Templates)
• Amazon AWS CFN (Cloud Formation) Templates

Higher level,

Terraform and Vagrant (for Devs)

• Google CoreOS
• Ubuntu Snappy
• RedHat Atomic

• Mesosphere Enterprise DC/OS
  • Apache Mesos (distributed systems kernel)
  • Apache ZooKeeper (distributed coordination)
  • Apache Marathon (container orchestration)

Docker focuses on ephemeral container’s and single process as a practice for application isolation. 

However, LXC now LXD, diverged to focus on overall system density by isolation of the OS itself. Because of this, in my view, LXD lends itself to vendor packaged and data enterprise solutions.

The technologies are designed to be compatible so you can take advantage of OS isolation through LXC with Docker running inside.