Data replication to scale reads

[Brayden]

Because Durable Objects are limited to 1,000 RPS, having a built-in feature to scale reads via data replication could serve as a strong offering for scaling usage.

Things to consider would be where the logical components live, and which instance(s) get to decide on data handoff as they ingest incoming data. How do we declare a main source? Is it a primary write, distributing each read to the replicas perhaps by way of web sockets? A lot of questions, some with clear answers others needing to mull over in more depth.

Placing this discussion here as a placeholder to come back to as I chew through the thoughts.