Whereas some builders are quitting Golang, Google’s open-source programming language has not misplaced all its floor but. Many corporations nonetheless swear by it for a few of its advantages, and INDMoney appears to be one in all them.
On the DES 2025 summit, Kausal Malladi, head of engineering at INDMoney, revealed the delicate expertise behind the investing platform’s capability to ship high-frequency market knowledge at extraordinary speeds. Dealing with over half 1,000,000 value ticks per minute—scaling as much as 2.5x throughout funds days or election outcomes—calls for greater than only a sturdy backend.
For INDMoney, the answer lies in a trio of open supply applied sciences: Go programming language, the messaging system NATS, and a finely optimised in-house WebSocket engine. The corporate’s goal is to maintain merchants up to date in actual time, sustaining latencies beneath 200 milliseconds.
Value charts, AI-driven chart sample detection, and prompt alerts all draw from the identical flood of tick knowledge. “Milliseconds matter,” Malladi stated, noting how even a one-second delay can kill a buying and selling alternative. The corporate described how they’re doing all of it whereas having a lean infrastructure.
Huge on Go Programming and Open Supply Tech

“Go helps with loads of simplistic use circumstances. Go runtime has an excellent functionality that it really works with fewer sources. It doesn’t want extra working system sources,” Malladi advised AIM.
He famous that one can use Go to energy a leaner infrastructure extra successfully.
Malladi highlighted that if one makes use of Go for an software, the language itself consumes minimal system sources—a lot of the useful resource utilization is devoted to the applying’s precise duties.
He emphasised that Go has good capabilities, like Go routines, which allow builders to facilitate parallel processing whereas working with a considerable amount of knowledge.
INDMoney’s real-time system ditched monoliths in favour of decoupled microservices, every shouldering a definite accountability—streaming, evaluation, alerts, or rendering charts. “So all of them might nonetheless be powered utilizing one single monolith,” Malladi stated. Nevertheless, the danger for downtime is excessive with this strategy, which is why they take a decoupled strategy.
Malladi said that Go’s light-weight concurrency mannequin helps run these companies with minimal overhead, even on infrastructure smaller than a few common trendy smartphones.
A key part is multicast streaming. Ticks from exchanges are acquired by way of on-prem multicast after which despatched to AWS EC2 cases grouped below a multicast handle. Every node independently receives the information—no further hops, no relay bottlenecks. Go handles this fan-out effectively, and NATS acts because the open-source spine that ensures messages attain each consumer or downstream service reliably.
NATS helped the group construct a “very dependable infrastructure”, with fast setup, excessive availability, and JWT authentication out of the field. “It may be arrange in a few days, with out a lot effort,” he added.
To ship this knowledge to customers, INDMoney constructed its personal WebSocket server atop the Gorilla toolkit. The system helps JWT-based authentication and was stress-tested utilizing pprof to pinpoint CPU bottlenecks. In a single case, reminiscence profiling revealed a single map lock dragging down efficiency. Switching to Go’s sync.Map lowered useful resource consumption by 75%.
Engineering for Each Millisecond
The corporate’s intention of decreasing latency prolonged into serialisation, networking, and even how clocks are synced. Protobuf, one other open-source tech by Google, changed JSON in knowledge payloads, chopping transmission measurement by over 50%. Past CPU or reminiscence, community throughput grew to become a key monitoring metric.
To ensure user-facing latency matched backend efficiency, the group applied client-side sampling. “Not each clock on the planet is identical,” Malladi added, prompting them to introduce time changes for correct measurements. In addition they used Cloudflare’s Argo Sensible Routing and multiprotocol label switching (MPLS) to optimise supply routes.
Fallbacks are in every single place. If NATS goes down, the WebSocket system picks up the slack. If a service crashes, microservice isolation ensures the remainder keep reside. Even knowledge subscriptions are dealt with intelligently. Map-heavy operations, like managing who subscribed to what, are accomplished with most concurrency security and minimal locks.
Why it Works
It’s not nearly Go, it’s about utilizing the precise instruments, profiling, and planning for failure. Simplifying programs, fallback engineering, all the time have one thing or the opposite as a fallback so that you just don’t find yourself operating into disasters.
INDMoney’s stack consists of NATS, Gorilla WebSocket, Redis, Protobuf, and even Cloudflare, however the structure stays pragmatic. Every half has a function, and every fallback has a narrative. On the centre of all of it, Go offers the efficiency baseline and concurrency flexibility the system calls for.
“We favor utilizing open supply expertise, however we additionally advocate for constructing in-house, like our WebSocket server,” Malladi stated to AIM, affirming that open supply enhances their very own work.
The publish Why INDMoney is Utilizing Golang to Energy Actual-time Information Streaming appeared first on Analytics India Journal.