INACASH
Backend Engineer · Fintech · 2023–2024
Payment services across five channels in production, where every transaction has to add up.
2 hoursTo restore a production Redis outage
Zero data lossDuring that incident
5 channelsOne module per channel
Payment flow
ChannelsQR-code payments · virtual accounts · bill payments
Go servicesACID transactions
PostgreSQLLedger
RedisHot-path cache
Google Pub/SubEvents
Incident recovery
A production Redis outage hit partner integrations. I restored service within 2 hours with zero data loss.
Consistency
High-availability services with strict ACID guarantees on transaction data.
Latency
A Redis caching layer on the high-frequency transaction pipelines.
Stack: Go, PostgreSQL, Redis, Google Pub/Sub, Docker, GCP.