3 ms·
I think that within a datacenter, a bunch of microservices make sense. When communicating with a customer, you want to craft just the data they need and minimiz
by shanemhansen 10y ago
I think that within a datacenter, a bunch of microservices make sense. When communicating with a customer, you want to craft just the data they need and minimize roundtrips.
GraphQL seems to be a great candidate for bridging this gap. I recommend using graphql to allow clients can use to make "One Special Bigger Request" which then gets split into multiple requests on the backend.
- KirinDave 10y agoI see no reason why this isn't compatible with gql. But even then, gql is hard to architect right unless you fence off a rather minimal subset of it.
- derefr 10y agoThe thing about One Special Bigger Request is that it isn't cacheable. GraphQL is no exception: https://philsturgeon.uk/api/2017/01/26/graphql-vs-rest-caching/ https://philsturgeon.uk/api/2017/01/26/graphql-vs-rest-cachi... If you want network-level caching, you want multiple atomic resource requests. HTTP2 enables this.