Jova Resto
A restaurant POS built as microservices, with an Android app that keeps selling when the connection drops.
- Type
- Internal and SaaS
- Stack
- Android, Laravel, Go
- Year
- 2022 to 2026
- Role
- Backend and Android developer behind the admin platform that runs every subscribed outlet, the kitchen display, the Redis Stream sync pipeline and the Android POS.
The problem
Outlets on unstable connections kept retrying their sync, which duplicated transactions, and a single POS process could not serve every outlet at once.
What I decided
- Split the platform into six services with clear edges: core POS, admin, kitchen display, a Kafka bridge, an ingestion service and a Laravel consumer.
- Made Redis Stream ingestion idempotent on the order id, with stream trimming and a health monitor, so a retried batch changes nothing.
- Built the Android POS offline-first on Room, printing to ESC/POS over Bluetooth and reconciling shifts and cash on the device.
Where it landed
At the latest snapshot: 1,789,004 transactions, Rp 83.18B GMV and 3,239,203 order lines across 885 outlets, averaging 2,518 transactions a day from 73 active brands a month. Payment reconciliation covers QRIS and Doku.
All projectsNext project: Jova POS
Client systems stay private: no source code, internal URLs or production screenshots appear here. Every figure comes from the repositories or a read-only count on the production database.