Closed KyleAMathews closed 1 year ago
So sorry for the slow reply here. We don't often get questions in the form of issues and somehow this slipped by.
This only works if everyone gets the same pull response. But Replicache is designed to allow the pull response to be customized.
I think scaling reads is something databases are pretty good at. Can you give a sense of the scale you are worried about?
If you're still interested in this question come find me at discord.replicache.dev - happy to discuss more.
If you have a lot of connected clients, all of them pulling at the same time can add a lot of load to your db (probably necessitating setting up some sort of caching layer. It seems like it'd be nice to able to cache responses instead on the CDN. I was thinking of a scheme like this:
Thoughts?
The tricky bit is the lastMutationId — perhaps that could be a separate request the client makes when it has an unconfirmed mutation locally?