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
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 implemented forward/reverse lists, counts, and indexes slightly differently. Retries and out-of-order events caused subtle drift. Migrations became error-prone because the "rules" for derived data lived in application code scattered across services.
That's what Actionbase does: versioned state transitions, pre-computed indexes, idempotent mutations—all in one place. If your current setup is working and correctness isn't drifting, you probably don't need this.
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