TAG
#integration-patterns
8 posts
-
The Boundary Principle: Integration Is Border Work
Every integration lives or dies at one seam: a clean, watched translation layer at the edge. Let the wire format leak past it and the system rots.
-
EDIFACT, HL7v2, and the Protocols That Refuse to Die
REST and JSON didn't kill the old formats. EDI still moves most B2B transactions, HL7v2 still runs hospitals. Integration is bridging old to new, forever.
-
From PNR to Order: Integrating Airline Distribution Without Losing Your Mind
A 1960s record format, an 1980s messaging standard, and a new XML API that half the airlines support. Travel integration means bridging all three at once.
-
The Dual-Write Problem: Why Your Event Never Fired
You updated the database and published an event. One of them silently didn't happen. This is the bug behind half the 'data out of sync' tickets we get.
-
Outbound-Only: Cloudflare Tunnels as a Zero-Trust Integration Layer
Connecting a legacy on-prem system to a cloud API used to mean months of firewall negotiation. Outbound-only tunneling makes that number zero.
-
Why Your iPaaS Won't Save You
Low-code integration platforms promise everything. They deliver dashboards. Here's what actually works after 20 years.
-
Draw the Line: What Belongs in an API Gateway
A gateway routes, authenticates, and rate-limits. Everything else is business logic in the wrong place. Here's the boundary we defend on every project.
-
There's No Turnkey in Integration
API platforms give you 70% on day one. The other 30% is where projects fail. Why requirements engineering beats tool evaluation.