I guess it's just a matter of putting auto-resolvers somewhere generic and calling some-adapter/generate-resolvers with the set of attributes that you want for that adapter? https://github.com/fulcrologic/fulcro-rad-demo/blob/1ba6973b2a461f2db9d75d7ab0f529432177d278/src/sql/com/example/components/auto_resolvers.clj#L14=

It is designed for exactly that use-case.

RAD front-end knowns nothing about real data sources, only EQL queries, and the back-end is designed (queries and even with form save) to be able to hit any number of databases.

Thanks @U0CKQ19AQ. Going to try a mix of a document db for the bulk of the application logic while using SQL for heavy report/chart queries.