4 ms·
I love the idea of Durable Objects, and have thoughts about it in the health space (although having a single provider of them is probably a bad thing) but cross
by robertlagrant 2y ago
I love the idea of Durable Objects, and have thoughts about it in the health space (although having a single provider of them is probably a bad thing) but cross-cutting questions such as this seem to be quite difficult to achieve.
From the chat logs example in your article: how do you cope with a requirement such as "I as a user want to see all my latest thread activity in one place, across all my chat rooms?"
- korkybuchek 2y ago> From the chat logs example in your article: how do you cope with a requirement such as "I as a user want to see all my latest thread activity in one place, across all my chat rooms?" create a copy, for example
- jmull 2y agoThat's an easy case: write to two places (one for the chat and one for the user's activity). In this case I think you can let them become inconsistent in the face of, e.g., write errors.
- NathanFlurry 2y agoThis. > In this case I think you can let them become inconsistent in the face of, e.g., write errors. For devs using CF Durable Objects, people frequently use CF Queues or CF Workflows to ensure that everything is eventually consistent without significant overhead. It's a similar pattern to what large cos already do at scale with keeping data up to date across multiple partitions with Cassandra/DynamoDB.