Comment by em3s

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) with slightly different implementations. Counters drifted, toggle logic varied, indexes duplicated.

If you have one team and one use case, ScyllaDB could work well. Our problem was multiple teams hitting the same walls repeatedly.

That said, HBase is just the storage backend—Actionbase is the interaction layer on top. We'd consider ScyllaDB as a backend too. Currently HBase is battle-tested in production, while SlateDB would need dev effort. We'd love community input on direction: https://github.com/kakao/actionbase/discussions/144