In production
FedEx SOAP-to-REST Proxy
Problem
FedEx retired the legacy web services our shipping integration depended on. The internal systems generating shipments only spoke SOAP, the new FedEx APIs only spoke REST, and losing the integration meant shipping would stop.
Constraints
The legacy systems could not be rewritten on any realistic timeline, and the deadline was FedEx's, not ours. The fix had to be invisible to the existing systems: same requests in, same responses back.
What I Built
A translation proxy in Node.js that accepts the legacy SOAP requests, maps them to the modern FedEx REST API, and returns responses in the exact shape the old systems expect. The first working version came together over a weekend. It has been hardened since, but the architecture has not changed.
Outcome
Shipping never stopped. The proxy has been in production since, and the legacy systems still have no idea the API they rely on no longer exists.