![]() These data layer will hide underlying services, we can name fields as our liking, abstract implemented details, relate data from data sources but need not expose their other sources to clients and create data layer for clients. Single client accessing multiple datasources : eg 3 REST APIs, Json file and database system etc., here GraphQL will unite those data source into a data layer.However, with GraphQL, it allows client to share core data but they can ask for data field that they want to access and not burdened by data needs of other applications. Multi client sharing single datasource: When web and mobile app both need to access shared datasource, but views differs in both app, and have different interfaces, then REST APIs between these 2 clients can result in bloated endpoints with unnecessary data of other clients.GraphQL - There are mainly 2 use cases for GraphQL: Also, at some point we need load balancing, custom authorization monitoring, here GRPC provides building blocks with default implementation and extension points. ![]() Or the use case, where, if backend system talks to 100s of microservices, GRPC offer efficient speed, and provide built in features like deadline propagation, cascading cancellations retries, request hedging, provide streaming APIs to stream multiple request/response in 1 RPC interaction.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |