Thank you for the detailed response. That clears it up for me 🙂 - It would be awesome if this could
Thank you for the detailed response. That clears it up for me 
- It would be awesome if this could be captured in the docs.
- My problem is almost certainly that I'm not using the sessions API.
The docs to me imply that the sessions API is to guarantee sequential consistency for a set of queries, but the bulk of my traffic is pulling a single field out of the database so I don't actually care about sequential consistency in a lot of cases.
Feel free to point out if I'm missing the obvious, but I don't think the docs make it clear that the sessions API is required for queries to hit a read replica.
I'll go add some
- It would be awesome if this could be captured in the docs.
- My problem is almost certainly that I'm not using the sessions API.
This is not concrete. What is quiet, and what is "still receiving queries from all over"?What I was trying to convey is that there is consistent non-zero traffic in every region, and that I expected read replicas in every region to be queried. "Quiet" as in "not enough to overload the primary DB".
The docs to me imply that the sessions API is to guarantee sequential consistency for a set of queries, but the bulk of my traffic is pulling a single field out of the database so I don't actually care about sequential consistency in a lot of cases.
Feel free to point out if I'm missing the obvious, but I don't think the docs make it clear that the sessions API is required for queries to hit a read replica.
I'll go add some
.withSession() calls to my worker and see what happens. Thanks again.






