Engineering with the platform's global loyalty and rewards teams: migrating legacy systems to event-driven microservices in Go, across point tracking and the ledger — distributed systems work through to war-room production deployments.
A global loyalty & rewards platform2 min read
Hover or focus a component to see what it is and what it talks to. Arrow keys move between them.
Legacy points-and-rewards systems migrate onto event streams built as Go microservices, feeding a ledger of balances and global member APIs.
Components:
Connections:
The situation
Loyalty and rewards at the platform's global scale run through systems where correctness is non-negotiable: points are money, and the ledger is the record. Migrating legacy systems of that importance to a modern architecture has to happen without breaking the accounting underneath millions of members.
What we did
How it works
We worked with the global loyalty and rewards teams to migrate legacy systems to event-driven microservices written in Go. The work ran across point tracking and the ledger — deeply distributed-systems engineering, where event ordering, idempotency, and reconciliation decide whether the numbers stay right. It carried through to production: war rooms for deployments, where the migration met live traffic.
Outcome
Legacy loyalty systems replaced by event-driven Go microservices across point tracking and the ledger — modern architecture running inside one of the world's largest financial services platforms, deployed to production and proven there.
Stack
Related services
Strategy. Software. Systems.
Describe the system — what it has to do and what it has to survive. An engineer replies within one business day.
Book a callOr describe it here
One line is enough. A person reads it and replies within a business day.
