Gojek's Evolution of Bid Notifications to Courier
Original post Evolution of Bid Notifications to Courier
Article Summary
Gojek was sending 97-99% of driver bid notifications successfully. They rewrote the system and hit 99.9%+.
Gojek's engineering team migrated their critical bid notification system (connecting hungry customers with drivers) from a third-party vendor to their in-house MQTT solution called Courier. They rolled out the change strategically across tier 3, 2, and 1 cities.
Key Takeaways
- Achieved 99.9%+ delivery rate vs 97-99% with the old vendor system
- Reduced P99 bid acceptance latency by 22% after the migration
- Consolidated three channels (Vendor, FCM, APNS) into Pusher with Courier
- Redesigned MQTT topic structure to eliminate device ID dependency issues
By replacing their vendor with an in-house MQTT solution, Gojek improved notification delivery to 99.9%+ and cut latency by 22%.
Continue reading
Software Mansion
Aug 26, 2026
More from Gojek
Project Butter: A Journey for App Performance Improvement
Gojek
Jan 6, 2026
Also on iOS
General Availability of Mobile Platform Support Arrives in Discord Social SDK Version 1.10
Discord
Aug 6, 2026
What This Article Covers
Gojek's push notification system depended on a third-party vendor. When they tried to migrate to Pusher, the Device ID integration with their internal microservices databases caused reliability problems and made the migration process harder than expected.
Ajat Prabha's team redesigned the MQTT publish topic structure to remove the deviceID dependency. This simplified the architecture and made the system more reliable.
They rolled out the changes gradually across tier 3, tier 2, and tier 1 cities. The migration worked well, and Gojek was able to consolidate three separate channels (Vendor, FCM, APNS) into a single Pusher solution powered by Courier.
This page summarizes “Evolution of Bid Notifications to Courier” by Gojek, published Dec 8, 2023. All credit for the original work goes to the authors.
