Why not just use Redis (or sorted sets)?

[em3s]

Redis sorted sets can model interactions—we know.

The problem we faced wasn't "can Redis do this?" It was the same pattern being rebuilt across teams—different key schemas, different expiration policies, different counting logic. Actionbase enforces a domain model—who did what to which target—so interactions become portable across services.

On storage: at Kakao, two options could handle our scale—HBase and a Redis-compatible distributed store. We chose HBase because we had too much existing data to fit on a single node and needed bulk loading for migration. That said, the codebase has a storage abstraction layer (get, scan, batch, checkAndMutate for distributed locking)—Redis should work.

For smaller setups, Redis works well.

[em3s]

If you dig into the codebase, you'll find the storage abstraction. Not production-verified for Redis, but if someone wants to implement and test it, contributions are welcome. Curious—what's your threshold for "Redis is enough"?

[em3s]

This Q&A was pre-written in preparation for the public release. Closing now—looking forward to real questions from the community.