3 ms·
Good question. I like the idea of having a configuration that includes optimistic writes and perhaps even reads from localStorage for projects that have very lo
by pancomplex 3y ago
Good question. I like the idea of having a configuration that includes optimistic writes and perhaps even reads from localStorage for projects that have very low latency/unstable network requirements.
That being said, the server is blazingly fast as it leverages Redis and Fastify under the hood. In most of my testing, even on WiFi in SF with a server in Oregon, I would achieve <20ms reads/writes.
- joshstrange 3y agoTotally fair point and I understand that as-is it’s way simpler than what I proposed. I just know there are places I have to change a whole chain of functions from sync to async to use this (not the end of the world). I’m tempted to rewrite the backend in lambda+dynamoDB for a completely serverless backend (though for anything serious you’d probably want provisioned lambdas to avoid the cold start).
- pancomplex 3y agoThat sounds super useful. If you follow through with it feel free to open a PR with either code or a link to an AWS recipe. Ideally we have as many different server and client implementations as possible in the monorepo.