Microservices, Containers, Docker and a Cloud-Native Architecture in the Middleware World

In April 2016, I had two talks at JPoint in Moscow, Russia. The first talk was an existing talk about “How to Apply Big Data Analytics and Machine Learning to Real Time Processing”. The second talk was a brand new one: “Microservices and Containers in the Middleware World”. This article discusses and shows the new slide deck about how middleware is related to Microservices, Containers, Docker and Cloud-Native Architectures.

Key takeaways of the talk:

  • A cloud-native architecture enables flexible and agile development
  • Modern middleware leverages containers, Microservices and a cloud-native architecture
  • Just using Jenkins and Docker is not enough

A Cloud-Native Architecture for Middleware

Cloud Native development and deployment enables:

  • Scalable services
  • Resiliency
  • Automatic load balancing and failover
  • DevOps
  • Usage of public cloud platforms, but also private or hybrid
  • Vendor-agnostic deployment
  • Shorter time to results and increased flexibility

With all this, you can focus on solving your business problems instead of spending your time with plenty of technical issues in ”static and inflexible legacy architectures”. The following requirements are relevant for building a cloud-native architecture:

Microservices and Containers

  • Independent Services
  • Flexible Deployment

Continuous Integration and Continuous Delivery

  • Scripting / Automatic Test and Deployment
  • Service Discovery
  • Dynamic Distributed Configuration Management

Scalability and Failover

  • Cluster Management (Scheduling and Orchestration)
  • Load Balancing (Server-side and Client-side)
  • Resilience Design Patterns

Cloud Native Platform

  • Self-Service Agile Infrastructure
  • Private / Public / Hybrid PaaS

Slide Deck from JPoint Moscow 2016

The slide deck discusses requirements for a cloud-native architecture, available platforms such as Docker, Kubernetes, Apache Mesos or Cloud Foundry, and how all these components are related to Middleware:

http://www.slideshare.net/KaiWaehner/microservices-containers-docker-and-a-cloudnative-architecture-in-the-middleware-world

As always, feedback appreciated!

By the way: This slide deck is also an “add-on” and update to my well discussed article of last year: “Does a good Microservices architecture spell the death of the Enterprise Service Bus?

Kai Waehner

bridging the gap between technical innovation and business value for data integration, workflow orchestration, and agentic AI.

Recent Posts

Data Integration vs Workflow Orchestration: Connecting Systems Is Not Coordinating the Work

Data integration and workflow orchestration get confused because both ship hundreds of connectors. This post…

6 days ago

Process Intelligence Landscape 2026: Mining, Orchestration, and the Agentic AI Shift

Process intelligence has become three things, not one: mining, orchestration, and a decision gate. Here…

2 weeks ago

When to Use AMQP, JMS, Kafka, or MQTT: Trade-offs, Not a Winner

AMQP, JMS, Kafka, and MQTT get compared as rivals, but a message broker, a log,…

2 weeks ago

Kafka vs Flink vs Spark: Do You Really Need Real-Time?

Most vendors sell milliseconds, but most enterprise use cases do not need them. A critical…

3 weeks ago

Edge to Cloud and Back: Four Data Movement Problems, and Why One Technology Never Solves All of Them

Edge to cloud is not one integration problem. It is four: telemetry going up, control…

3 weeks ago

Data Integration Landscape 2026: Event Streaming, API, and Batch in the Era of Agentic AI

The Data Integration Landscape 2026 maps every major vendor across three communication paradigms: request-response, event-driven,…

4 weeks ago