Virtual Actor state query and write performance pain points
Problem
When using the virtual actor model, users must maintain multiple databases to query state, causing state redundancy and schema change risks; additionally, write latency is about 100ms, which is not suitable for real-time applications, contrasting with Celld's ~1ms write latency.
Pain points
- Virtual actor state query requires redundant databases and is sensitive to schema changes
- Write latency of about 100ms is unsuitable for real-time applications
Questions to verify
- Have you encountered redundant state query issues with virtual actors in real projects?
- What is your tolerance for write latency?
Evidence
quote
Looks great but one of the common problems with the virtual actor model is state query. It's all well and good to have nice separated state dbs but for most use cases that means further double up on storing the state again in another database that can query it. I don't think anyone has come up with a nice solution for this problem without using a loose document database, but even then actors can change their schema.
quote
100ms for a write - not usable for anything beyond toys. I mean we have https://github.com/denoland/celld - with a known good open source history. Durable writes there are as low as 1ms.
Disclaimer: this card is distilled by AI from community discussions as “pain point evidence”. It is a starting point for need analysis and validation, not a “validated market need”. AI has analytical limits; please open the original discussion above to manually verify before key decisions.