De Facto Leader Emerged

Emerging

Security Scanning

Scan for viruses, missed hardening and accidental data leakage. Varies depending on your needs, but there are some free scanning services now.

UpGuard (reviewing)

Security Intrusion Detection

Look for any intrusions in the system.

Synthetic Monitoring

• Dynatrace

Health Check

System Monitoring

Application Insight Monitoring

Look inside the code to determine performance and support Production problems inside the code.

n/a

Microsoft Azure - Application Insight (free and powerful)

Dynatrace was previous winner for stand alone.

• Cloud Provider Module
  
  

• Dynatrace

• CA APM (previously Wily Introscope)

Integrity Verifciation

Confirm and audit any changes to the system.

DOS and DDOS Mitigation

There is some argument that going true cloud no longer requires this. I'm not convinced.

n/a

Akamai.

However, for smaller implementations Cloud Provider built-in services may be enough.

• Akamai

• VeriSign

Customer Caching

Take load off of your system.

Elasticity

Akamai.

However, for smaller implementations Cloud Provider built-in services may be enough.

• Akamai

• Cloud Providers

Orchestration of Containers & Service Discovery

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

Elasticity

• 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)

Application Packaging

Means to create application packages and manage centrally.

Zero Footprint AppDev Model

Automation and configuration that travels with the application. There is some overlap here with configuration management, but I believe in keeping them separate.

• Zero Footprint with Scripts

• Habitat

Software Defined Network

Infrastructure as Code.

Cloud Provider Module or Container Technology

• Microsoft Azure

• Amazon AWS

• Google Cloud Platform

• Rackspace

• HashiCorp Console

Virtualization Cloud Provider

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.

n/a

At the moment (2016)

Microsoft Azure for ease of use.

• Microsoft Azure

• Amazon AWS

• Google Cloud Platform

• Rackspace

Environment Configurator

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)

Remove infrastructure dependency.

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

• Ansible

Continuous Code Testing

Continous Infrastructure Testing

• Chef Kitchen

Code Unit Testing

jUnit

Continuous Integration & Deployment

When build completes auto deploy and hook up. Be the workflow engine to manage CI/CD pipeline from source to delivery

• Jenkins

• Bamboo

Continuous Build

Building Application Virtualization from Recipes. Think entire ecosystem (not just code) is built from recipes.

• Jenkins

• Bamboo

Source Control for Code

Bitbucket or direclty GitHub

• GitHub

• Bitbucket (Atlassian Product fronting GitHub)

• Mercurial

• Subversion (Does not scale for Agile well)

Packer

Centralized Log Aggregation and Alerting

Simplification of adapters to be pipeline will likely emerge as part of Cloud Providers and container technology.

Remove infrastructure dependency.

Splunk

Application Caching System

Lots of noSQL databases in this space.

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

Messaging System

Guarantee delivery and integrity of key transactions across systems.

Depends on your specific messaging needs.

Will break this up later.

• Kafka

• RabbitMQ

Application Virtualization

Microservices concept of running ephemeral containers at the focusing on escalating a single immutable application.

• Building from Recipes

• Linking of Containers

Docker

• Docker

Configuration Management and Building Applications and Integration from Recipe

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

Automation of Cloud Infrastructure

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.

Infrastructure as Code

• Azure ARM (Azure Resource Manager Templates)

• Amazon AWS CFN (Cloud Formation) Templates

Higher level,

Terraform and Vagrant (for Devs)

Optimized Operating System for Containers

Newish concept of lightweight transactionally updated operating system. Solaris had the transactional aspect a while back.

• Google CoreOS

• Ubuntu Snappy

• RedHat Atomic

Distributed Operating System for Containers

Similar in concept to what Hadoop technology solves for databases.

Elasticity

• Mesosphere Enterprise DC/OS

  • Apache Mesos (distributed systems kernel)

  • Apache ZooKeeper (distributed coordination)

  • Apache Marathon (container orchestration)

Operating Virtualization

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.

Cloud Density

LXD (LXC)