When should I NOT use Actionbase?

[em3s]

• A single database instance handles your workload
• You need general-purpose graph queries or traversals
• Your team doesn't have HBase operational experience
• You're not hitting scaling walls yet

At Kakao's scale, this became necessary. At smaller scale, a well-tuned RDBMS is almost always the better choice.

[em3s]

One thing we haven't fully documented: when write amplification becomes a problem. We're still gathering data on the trade-offs of write-time materialization. If you've dealt with similar patterns, curious what signals you watch for.

[em3s]

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