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
I've been using Claude Code for my research notes and had the same realization, it's less about perfecting prompts and more about building tools so it can surprise you. The moment I stopped treating it like a function and started treating it like a coworker who reads at 1000 wpm, everything clicked
Mandiant releases rainbow tables for a 25 year old broken protocol because enterprises still won't disable it. It seems like sometimes the best security tool is just making the risk impossible to ignore.
Also since firefox is FOSS and any model has reasonably been trained on the code base of at least Firefox if not also Chromium, it's not a shock that agents are able to generate a similar code!
Finding out "computer" was a job title because precise calculation was so hard to find makes me feel less bad about needing a calculator for basic arithmetic.
