@michaelcompton You discussed Apollo Federation:
It’s able to be done already by putting an Apollo server as a proxy in front of your Dgraph instance. That’ll take a small amount of boilerplate, but I currently feel that if you are building an Apollo federation, it’s likely that you have the capability for that, and it’s a more Apollo native solution than us baking it in. (we have a blog coming soon around this)
Did the blog post about using DGraph as a leaf of a Apollo Gateway’s federation get posted?
We also wondered if there was any discussion or examples about using DGraph as a caching gateway for GraphQL queries?
We use traffic shadowing with Apollo Federation (and Apollo Gateway) and compare the differences in responses between the legacy Python implementation and our new Go GraphQL backend service.
After our port is complete, we wouldn’t need side-by-side comparisons, so we could then evaluate also using DGraph as a gateway instead of Apollo. I would be very interested in any sort of performance comparison (Apollo Gateway vs DGraph-as-a-gateway) or demonstration of DGraph-as-a-gateway.