PlanetScale Portals: Read-only regions

Looks like a nice launch for apps that need lower latency for reads. A noticeable omission from the blog post is how these replicas impact consistency. Won't reads from read-only regions have a weaker consistency than you typically get with Vitess/PlanetScale? I'm guessing weaker than read-your-writes.

Not directly related, I&#x27;ve been really tempted by all these exciting new database offerings.. PlanetScale, CockroachDB, FaunaDB.. but there don&#x27;t seem to be any solid (node.js) background job queue libraries that support them. I really want to take advantage of these low dev-ops high availability offerings, but I don&#x27;t want to have to tack Redis onto my stack just so I can use BullMQ, with data persistence and robustness as a bit of an afterthought.<p>And I don&#x27;t want to roll my own because it&#x27;s not a trivial thing to solve, especially with stall detection etc.<p>I&#x27;d love to just have one robust data-store.<p>Am I missing something?

The automatic routing via Rails is very cool. I may try to work that up in Django as well.

This would be such a nice addition to apps deployed on fly.io

What kind of consistency guarantees does this offer?