I had a brand new talk at OBJEKTspektrum Information Days 2013 in Frankfurt and Munich this week: Enterprise Integration Patterns Revisited. I wanna share my slides with you.
Applications have to be integrated – no matter which programming languages, databases or infrastructures are used. However, the realization of integration scenarios is a complex and time-consuming task. Over 10 years ago, Enteprise Integration Patterns (EIP) became the world wide defacto standard for splitting huge, complex integration scenarios into smaller recurring problems. These patterns appear in almost every integration project.
This session revisits EIPs and gives shows status quo. After giving a short introduction with several examples, the audience will learn which EIPs still have a „right to exist“, and which new EIPs emerged in the meantime. The end of the session shows different frameworks and tools which already implement EIPs and therefore help the architect to reduce efforts a lot.
You are currently viewing a placeholder content from Default. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
AI agents fail in production when they are connected directly to raw event streams. Flink…
Complex Event Processing is the most underused capability in Apache Flink. It detects meaningful event…
MCP, REST/HTTP APIs, and Apache Kafka are not alternatives. They solve different problems at different…
The Enterprise Agentic AI Landscape 2026 maps every major AI vendor across two dimensions that…
Agentic AI without governed processes is fast but ungoverned. Event-driven integration without process intelligence moves…
Two toolchains, two skill sets, two CI/CD pipelines — that has been the reality for…