I’ve been exploring the options for global deployment of Hydra and it seems that the path of the least resistance (but not resistance-free, of course) is to use CockroachDB.
Let me quickly define what I mean by global deployment: multiple regions, some paired regions (in Azure terminology), global clients, ideally the tokens that could be used in multiple regions - at least in the ones that are close enough.
Opaque token implies that we would need very very quick DB lookup because it happens on each API call. I am new to CockroachDB but my understanding is that normally a read requires network roundtrip to the leaseholder. Leaseholder holds a lease for a specific range of keys, so, this potentially means constant roadtrips across the world for each token - the clients from the same range will be in different locations, randomly distributed.
So, here is the question: I see that CockroachDB has multiple topology recommendations, including the Follower Reads Topology. Are there any recommendations on CockroachDB configuration, topology or any other suggestions for such a scenario?