Honestly, I think the eventually-consistent KV is suitable for many usecases. However, a similar product, but immediately consistent, which was just for small info, integers and such, might be useful. I’m thinking along the lines of treating each instance of a Worker like a thread, and having some sort of mutex / cmpexchg mechanism. If the resource is a) small, and b) not disk-backed, it might be doable.
Some things that this theoretical db could enable are:
- reference counting
- mutual exclusion / locking
- global stats counters
- global state machine latching
As for what one could do with this capability? Well, I don’t like spouting buzzwords, but a blockchain’s state could be incremented and tracked globally without a centralized server.
There’s a lot of other fun decentralized systems problems that could be solved and deployed if that tool existed…
I rambled about one problem which it would solve: