3 points | by em3s 1 hour ago
2 comments
I built Actionbase at Kakao (KakaoTalk, ~50M MAU).
It started because the same features—likes, views, follows—were being rebuilt across teams, each hitting similar scaling walls.
It's been in production for years, serving Kakao services at over 1M requests per minute.
Our approach: precompute everything at write time. Reads are just lookups—no aggregation, predictable latency.
Currently backed by HBase. Lighter backends (e.g., SlateDB) on the roadmap.
Try it — just Docker:
docker run -it ghcr.io/kakao/actionbase:standalone
Genuinely curious: are there existing systems for high-volume interaction data (likes, follows, views) that I missed?
Happy to answer questions.
I built Actionbase at Kakao (KakaoTalk, ~50M MAU).
It started because the same features—likes, views, follows—were being rebuilt across teams, each hitting similar scaling walls.
It's been in production for years, serving Kakao services at over 1M requests per minute.
Our approach: precompute everything at write time. Reads are just lookups—no aggregation, predictable latency.
Currently backed by HBase. Lighter backends (e.g., SlateDB) on the roadmap.
Try it — just Docker:
Quick Start and production stories are in the README.Genuinely curious: are there existing systems for high-volume interaction data (likes, follows, views) that I missed?
Happy to answer questions.