GraphQL-Mesh vs GraphQL-Conductor

[BabakScript]

Hi @ardatan @dotansimha @Urigo

I see currently The Guild offers two solutions as GraphQL Gateway: GraphQL-Mesh and GraphQL-Conductor
Can you clarify which one is your recommended one to choose for a new project? Or maybe we can discuss a little here about the Pros/Cons of each tool to see when we should choose which one.

I see GraphQL-Conductor is written in Rust and I see a huge hype for Rust regarding performance. So I wondered if should we use GraphQL-Conductor rather than GraphQL-Mesh. But on the other hand, it looks like Conductor is still in the Alpha version so I think maybe it's not stable enough for production.

[Urigo]

GraphQL Mesh is the recommended solution for almost all projects.
It is the most feature complete and the most performant JS based gateway out there.
The number of companies who needs the performance boost of Conductor over Mesh are very few companies
Also then, it is actually easier to use GraphQL Mesh first and then migrate from it to Conductor.

[BabakScript]

Thanks for your clarification 😉
Makes sense.

[doloboyz]

What is the difference in use case between Mesh and Conductor. Does Conductor simply provide a performance boost over Mesh?

[Urigo]

Most of our users needed a gateway that replaces Apollo Router and GraphQL Mesh was a better and more complete choice for them
So we are focusing now on getting Mesh to v1.0 which will happen very soon and after that we’ll move back to Conductor.
We are aiming to have correctness and a good approach for implementing a Fed query planner and execution, and once this is done, we’ll tackle the performance requirements (probably by implementing the same approach for Conductor).
@doloboyz to your question - yes, it is mostly for a performance boost (which is required for very few companies as Mesh is pushing the performance of JS to extreme, compared to other implementations out there)