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:
Cloud Native development and deployment enables:
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
Continuous Integration and Continuous Delivery
Scalability and Failover
Cloud Native Platform
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:
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?”
Data integration and workflow orchestration get confused because both ship hundreds of connectors. This post…
Process intelligence has become three things, not one: mining, orchestration, and a decision gate. Here…
AMQP, JMS, Kafka, and MQTT get compared as rivals, but a message broker, a log,…
Most vendors sell milliseconds, but most enterprise use cases do not need them. A critical…
Edge to cloud is not one integration problem. It is four: telemetry going up, control…
The Data Integration Landscape 2026 maps every major vendor across three communication paradigms: request-response, event-driven,…