Clojurians Log v2

Hi, I am developing an app using react-native/expo (not settled yet), this app is a mobile first app. It is a re-frame app. The data needs to be stored locally first and data will also be loaded from local db. Data will be synced to server after the fact. I am exploring options for storing data locally, sql server seems to be one of the choices. Is there any other mature choice ? I would have preferred a persistent datalog compliant db for native development, are there any options in this regard ?

on the server my db of choice is crux only if I can find an equivalent db for the client side, otherwise will go for sql on both ends.

Breaking my holiday break to say that this interests me too. Happy to compare notes after the holiday week. We’re currently doing this by adding dozens of callback URIs...

crux with xodus or lmdb backend?

You'll need a redirector.

One central place that just forwards to where it's supposed to be.

I built a product that was multi tenant a few years back and we registered separate oauth credentials with our identity provider for each tenant domain. I realize that's more work but the isolation we ended up with was nice. We then automated all aspects of tenant provisioning so adding a tenant was still as simple as entering a name and clicking a button

I should add: our apps fetched their config for a tenant (like the oauth credentials) from another service at runtime so there wasn't any need to update settings / secret files with new credentials for each tenant.

But as dominicm said, if you want just one then you'll need a redirect that inspects some aspect of the state query param to determine the original tenant I think

There are a lot of services that offer rest+websocket apis but I find I usually want to work at a higher level then this. In my app I just want to be able to request or initiate streams of parsed, domain spec’d data, separately from the management of websocket/http connections. I suppose the protocols would look something like this:

(defprotocol X
  (request! [this msg ch] "request that receives exactly one response (on ch)"))

(defprotocol Y
  (send! [this msg] "(asynchronous?) send a message which may trigger response messages.")
  (recv-ch  [this msg ch] "return a channel of all response messages"))

There's plenty of services that don't allow that kind of dynamic registration. Although it maybe depends on how you're isolating tenants too

the hexagonal architecture might relate with your goal. are you familiar with it?

Nope, that looks like a good thing to research, thanks!

as an additional pointer, your core API might be better descirbed as pure inputs/outputs (data/data) instead of channels, streams etc channels and such are essentially FP-impure and preclude some techniques, especially related to unit-testing https://blog.ploeh.dk/2016/03/18/functional-architecture-is-ports-and-adapters/ is a good read!

So after thinking on it all day yesterday, I’m going down the route described above, namely encoding the origin domain into the state field sent to the auth server, and then writing an intermediate callback that will do nothing but decode the state, pull out the encoded origin domain, and redirect to the final callback at the correct domain.