Carrier Integration Software Architecture

Carrier Integration Software: Architecture & Reliability

Latest

Multi-Tenant Carrier Integration Migration to HTTP/3: Solving Connection Pooling and Observability Challenges Without Breaking Tenant Isolation

Multi-Tenant Carrier Integration Migration to HTTP/3: Solving Connection Pooling and Observability Challenges Without Breaking Tenant Isolation

DHL's APIs now support HTTP/3. FedEx has experimental QUIC endpoints running. UPS is evaluating QUIC for their tracking services. Your multi-tenant carrier integration middleware, serving 500+ shippers, suddenly faces a migration challenge that goes deeper than switching protocols. Traditional carrier integration middleware assumes TCP-based connection pooling, where

By Koen M. Vermeulen
RFC 9700 Compliance for Multi-Tenant Carrier Integration: Implementing Mandatory PKCE Without Breaking Tenant Isolation

RFC 9700 Compliance for Multi-Tenant Carrier Integration: Implementing Mandatory PKCE Without Breaking Tenant Isolation

RFC 9700, published in January 2025, fundamentally changes how OAuth 2.0 authentication works in carrier integration systems. The specification mandates PKCE (Proof Key for Code Exchange) for all authorization code flows, not just public clients, creating immediate architectural challenges for multi-tenant carrier middleware platforms serving hundreds of customers with

By Koen M. Vermeulen
Multi-Tenant Webhook Fan-Out Architecture: Isolating Event Streams Without Sacrificing Delivery Guarantees in Carrier Integration Systems

Multi-Tenant Webhook Fan-Out Architecture: Isolating Event Streams Without Sacrificing Delivery Guarantees in Carrier Integration Systems

When you've built multi-tenant carrier integration systems, you quickly learn that traditional webhook patterns break under the unique pressures of shipping APIs. Multi-tenant SaaS applications typically limit tenants to 1M events per day, and anything beyond should be throttled and deferred. But carriers routinely blast you with tracking

By Koen M. Vermeulen
Multi-Tenant API Versioning for Carrier Integration: Preventing Cascade Failures When Breaking Changes Hit Hundreds of Shippers

Multi-Tenant API Versioning for Carrier Integration: Preventing Cascade Failures When Breaking Changes Hit Hundreds of Shippers

Your traditional API versioning just became exponentially more dangerous. When a breaking change hits your single-tenant middleware, you fix one system. When it hits multi-tenant carrier integration middleware serving 500 shippers, you've got 500 potential failures cascading through your platform simultaneously. Most carrier integration platforms serve multiple shippers.

By Koen M. Vermeulen
Sender-Constrained Tokens for Carrier Integration: Preventing Token Replay Attacks in Multi-Tenant Middleware

Sender-Constrained Tokens for Carrier Integration: Preventing Token Replay Attacks in Multi-Tenant Middleware

The Postman workspace breach exposed 30,000 workspaces containing live API keys and access tokens. Developers had been saving production secrets—live API keys, access tokens, even sensitive healthcare records—in their testing environments without proper access controls. Meanwhile, threat actors exploited OAuth tokens stolen from the Salesloft/Drift integration

By Koen M. Vermeulen