Series
The Integration Series
How separate systems are joined, one pattern per post, from the Enterprise Integration Patterns catalogue: choosing a style at all, the channels and message shapes that decide the coupling, routing and transformation, the endpoint patterns everybody needs and few build, and how to see inside a running integration. Part of Under the Hood.
Choosing an Integration Style
Four ways to join two systems, and each one decides what breaks later. File transfer asks nothing of either system and sets a latency floor. A shared database removes the lag and makes the schema a contract nobody can change. Remote calls couple availability, so the caller fails when the callee does. Messaging decouples time and hands you duplicates, reordering and a much harder debugging story.
Coming soon