The notion that the GraphQL schema is an abstraction layer makes tools like GraphQL Mesh less attractive to me. The schema acts as an abstraction layer over your domain’s microservices, making it easier to refactor and optimize your underlying services while not changing the API that other teams and end-user apps rely on. They also own an GraphQL service that exposes the “public API” (not public to the world, just public to the rest of the company) as a GraphQL schema. The ideal architecture, to me, is that a team/org within your company owns several microservices for different aspects of their domain and uses gRPC to communicate between them. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |