em3s

3 ms·

1. 1.▲
   by em3s 8mo ago

   You might be right! ScyllaDB is a solid choice—eventual consistency is often fine for interactions. The friction we hit was less about storage and more about fragmentation: teams kept rebuilding the same features (likes, views, follows) wit
2. 2.▲
   by em3s 8mo ago

   You might be right! Kafka + KV store + Redis can definitely work for this. Our teams typically started with MySQL, then added Kafka and Redis as they scaled. The pain wasn't the initial build—it was what happened after: every team impl
3. 3.▲
   by em3s 8mo ago

   Hi HN, 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
4. 4.▲
   Show HN: Actionbase – A database for likes, views, follows at 1M+ req/min(github.com)

   8 points by em3s 8mo ago|5 comments