Delivery Tracking Gateway
The complete system record. Choose the proof lens that fits your role.
Choose The Proof Lens
One system record, three reader paths.
Feature-frozen3-act recordGitHub available
Business proofFounder / operator
One Gateway for DHL, DPD, and GLS Tracking
Replaced three carrier portals with one API and live tracking stream. Built for 100 active shipments, 500 events/minute, and sub-200ms fanout.
System FlowData ModelArchitecture LayersDecision Log
Open business proof5 min read
Architecture proofCTO / architect
Architectural Brief: Delivery Tracking Gateway
Carrier polling can return duplicates, stale events, and malformed payloads. The gateway keeps Postgres as the record and Redis as delivery.
System TopologyInfrastructure DecisionsConstraintsDecision Log
Open architecture proof6 min read
Technical proofSenior engineer
Why I Made WebSocket Delivery the Disposable Part of the Tracking System
Redis can disappear after Postgres accepts the event. The gateway had to make live delivery disposable without losing shipment truth.
Code SampleFailureConstraintSurprise
Open technical proof9 min read