APIs & back end
Parcel Pulse
A real-time shipment tracking API that merges updates from several couriers into one clean feed.
- Role
- Back-end developer
- Year
- 2025
- Stack
The challenge
An online store shipped with four couriers, each with its own tracking format, rate limits and outages. Customers kept emailing support to ask where their parcel was.
What I built
A small Go service that polls and receives courier webhooks, normalises every event into one schema and pushes live updates to the store and its customers over WebSockets.
Under the hood
Go for speed and low memory use, Redis for queues and rate limiting, PostgreSQL for history, and retries with back-off so a courier outage never loses an update. Shipped as a single Docker image with health checks and metrics.
The result
One API instead of four integrations, tracking pages that update on their own, and far fewer “where is my order?” emails.