Why your Microservices need GraphQL?

[@ngneerin]

How can you make use of populate functionality of mongoose to improve performance with graphql?

[@YourTechBudCodes]

Interesting question. We'll I haven't used Mongoose at all, but I guess populate is a feature to manage relationships. If I'm not wrong the same question can be extended for SQL joins. We don't want to GraphQL server to join the data when the driver/db can do it in an optimised manner. There is no easy answer here. The way we handled this problem in SpaceCloud is that we took control of the "Planning" step. Think of it as looking down the entire query tree then firing join queries upfront. In other words, you fire a different query to retrieve the posts when the author field is asked in its selection set vs when it isn't. This way we delegate the responsibility of joining data to the underlying database wherever possible. Hope that answers your question.

[@khaled_osman]

@@YourTechBudCodes so then when creating items in mutations you still need communication between the microservices to store the id references/relationships across the databases & microservices correct? federation will only handle the querying part and redirect it to to the corresponding microservice, but for mutations you need to handle that yourself

[@YourTechBudCodes]

Thats right. You need to handle that piece yourself. However, the mode of communication can be event driven or synchronous based on the requirement.

[@MeenakshiSekar]

Explained in a simple terms which made us to realize why graphql

[@YourTechBudCodes]

Glad you liked it

[@sureshvadapalli8251]

Thank you, Very Nicely explained. One question related to the orchestration pattern you explained... I have two different Microservices Customers and Products and each have a different database. I have a work flow orchestration layer that exposes one API endpoint and aggregates the response and returns it to the front end. If I use GraphQL to implement this use case, I still have to call the two underlying APIs and aggregate the result. correct? How does it help?

[@YourTechBudCodes]

Glad you liked the video. That is correct. Graphql provides you with the mechanism to join the results of the different endpoints together. All you need to do is write the logic to call each endpoint individually and not worry about stitching at all. This becomes even easier when using tools like SpaceCloud which will let you do all this without writing a single line of code.

[@alialsubaie8529]

Thank you 💗, keep it up buddy 👍

[@YourTechBudCodes]

Glad you liked it!

[@jasonalinton]

Incredible video

[@YourTechBudCodes]

Glad you liked it!

[@subrahmanyagurumurthy5083]

Thank you!

[@YourTechBudCodes]

Glad you liked it!

[@Nilesh_Narkhede]

Insightful..

[@YourTechBudCodes]

Thanks buddy

[@ayoadeabolaji9339]

Interesting... "GraphQL is to API Servers what SQL is to Databases"

[@YourTechBudCodes]

That's how I look at it. Thoughts?