In this article, I am not going to describe about under-the-hood connection of these stacks. I would suggest you stay tuned for that!

A common problem using gRPC and graphQL together along with MongoDB is that developer needs to creates a separate gRPC message; schema for graphQL; and mongo document. As this is the standard way, you can find this method in all the codebase with these stacks.

But the main question is, shouldn’t we just reflect back to the steps required to change the schema and mirror it in the system? If you are familiar with the concept of gRPC and graphQL, you would pretty much know about all the hassles to be made in each file.

#graphql #decorators