Naqrat — a conversion API rebuilt around events
A marketing platform that fell over under load, rebuilt as an event-driven system that absorbs millions of events per hour.
- Event-driven architecture
- APIs
- Marketing automation
The problem
The funnel's conversion API is the part of a marketing platform that cannot fail: every click, view and conversion arrives there, in bursts, at whatever rate the campaigns produce. Handling that traffic synchronously means the platform's stability is tied to its busiest second.
What I did
Rebuilt the platform around events: the API accepts and records the event, and everything that can happen afterwards happens afterwards. That turns a spike into a queue depth instead of an outage, and makes each consumer independently retryable.
Technical detail
Accept first, process after
The conversion endpoint's job is to take the event and let go of the request; the rest of the funnel reads it from there.
Stability as the deliverable
The point of the rebuild was not throughput for its own sake — it was that the marketing funnel stops losing events when a campaign does well.
Where it stands
The owner's figure for this work: the conversion API serves millions of events per hour and stays stable under load. No public benchmark has been published for it.
All projects