Design question. Why did you choose to front Hasura with Apollo instead of A) the other way around or B) no Apollo at all, and just use Hasura and APIs? I've got a decision to make about a platform, and I'm amazed by Hasura. Can I bother you for a few moments of your time as to how Apollo ended up in the mix? Clearly a low priority, but I'm awfully curious. Thanks!

Hi Steve! Great question - we use Apollo largely for schema stitching. In particular, we have a lot of custom query resolvers and mutations that are written in Python code, and Apollo allows us to easily take the auto-generated Hasura schema and stitch it with our custom routes.

Interesting. Thank you for the reply. I had been diving into the remote schemas functionality of Hasura, and since your prefect-server container pretty much migrates the database anyway, I was looking into an admittedly complex set of Hasura CLI actions (from Python so we're sort of doing exactly the same thing aren't we?!). I come from the "federate everything with Apollo" mindset myself, but was starting to see another way. Still, in terms of relative straight-forwardness, I can see your approach. Thank you again!

Yup anytime!