DAT Systems Moves from Kafka: The Full LavinMQ Story

LavinMQ's user story traces DAT back to its earliest days — three friends who set out to track field staff during Pakistan's February 2024 election, an effort derailed by an internet shutdown on election day. That setback led to a pivot: building a field-staff management system that worked over WhatsApp, Telegram, and WeChat instead of a custom app, since broadband access and digital literacy were limited among the intended users.

The strategy worked. Within eight months, DAT was working with the Lahore Waste Management Company, Pakistan's largest public-sector employer, with more than 16,000 employees.

Early on, DAT built its messaging backbone on Apache Kafka but ran into recurring reliability issues. After switching to LavinMQ, local memory usage in development dropped from 5GB to under 40MB, and the full migration was completed over a single weekend without downtime.

“It's not just a message queue for us,” said Ahsan Nabi Dar, CTO and co-founder of DAT. LavinMQ now underpins DAT's messaging, backups, inter-service communication, and parts of its HR and payroll processes, handling tens of thousands of daily messages across WhatsApp, Telegram, and WeChat.