4 ms·
This is unsuitable for real-world applications, where you will, inevitably, need at least a little mutable shared state. Async handles this reasonably well at a
by bcoates 11y ago
This is unsuitable for real-world applications, where you will, inevitably, need at least a little mutable shared state. Async handles this reasonably well at a decent performance cost; shared-memory threads (near-certain catastrophic failure) and database-only state (awful performance) do not.
The only real competition is transactional memory but it hasn't become mainstream yet.
- adamlett 11y agoI'm not sure what you're saying here exactly. What is unsuitable for real-world applications? I will say this, though, regarding the need for shared, mutable state: You can communicate by sharing memory, but you can also share memory by communicating. This is I guess what you allude to with database-only state, but it doesn't need to be a database. It could just as easily be a memcached server or some other fase key-value store.