RESOURCES
Field notes from the bridge.
What we learn from putting the translator in the network path. Protocols, performance, modernization, and the patterns we see most.
FROM THE BLOG
Blog·Legacy modernization
Why legacy SOAP services block modernization, and how to bridge them
SOAP is not the enemy. The cost and risk of rewriting the systems that depend on it is. There is a third path.
May 14, 20268 min
Blog·Architecture
Protocol translation vs API gateways: what is the difference
They look identical on a diagram, a box in the middle of your traffic. What they do to the traffic is fundamentally different.
Apr 30, 20266 min
Blog·Legacy modernization
Modernizing mainframe-era integrations for a cloud-native world
The mainframe is not going anywhere, and it does not need to. The integrations around it are what need modernizing.
Apr 16, 20267 min
Blog·Architecture
The case for a compatibility layer over point-to-point integrations
Every new integration feels cheap in isolation. The cost is in the graph they form together.
Apr 2, 20266 min
Blog·Observability
Observability for API translation: seeing inside the pipeline
When a request changes shape mid-flight, "it returned a 500" is not a diagnosis. You need to see every step.
Mar 19, 20267 min
Blog·Deployment
Sidecar vs centralized gateway: choosing a deployment model
The same logic can run as a shared service or a sidecar. The right choice depends on latency, blast radius, and ownership.
Mar 5, 20266 min
Blog·Performance
Reducing integration latency without rewriting upstreams
You cannot always make the upstream faster. You can stop the integration layer from adding latency of its own.
Feb 19, 20266 min
CASE STUDIES
Illustrative scenarios, honestly framed.
Composite examples representing typical situations, not named customers, not fabricated results.
Case study·Financial services
A financial-services org bridges legacy SOAP to a modern mobile API
A retail bank wanted a modern mobile experience. Its account and payments data lived behind SOAP it could not rewrite.
May 21, 20266 min
Case study·Retail
A retailer unifies partner APIs of inconsistent shapes
Every supplier integration spoke a slightly different dialect. The catalog team was drowning in special cases.
May 7, 20265 min
Case study·Healthcare
A healthcare provider modernizes mainframe integrations under compliance constraints
Patient data on a mainframe. A mandate to build modern clinical apps. A compliance team that could veto anything.
Apr 23, 20266 min
Case study·Logistics
A logistics company reaches private on-prem upstreams without opening firewall holes
The data lived behind a firewall. The cloud platform that needed it could not get in, and the network team would not open a door.
Apr 9, 20265 min
Case study·SaaS
A SaaS company consolidates fragmented internal API versions
Three live versions of the same internal API, dozens of consumers, and no one sure who was on what.
Mar 26, 20265 min