Tangential from a discussion in TFA about GraphQL:

> One benefit of GraphQL was to solve the “waterfall” problem of traditional REST APIs by allowing clients to ask for multiple pieces of data in one query. For example, instead of making three sequential HTTP calls:

    GET /user
    GET /user/friends
    GET /user/friends/photos

…you can write one GraphQL query to fetch it all at once.

Or you could have designed a schema to allow easy tree traversal. Or you could use a recursive CTE.

▲ pests 4 days ago | parent [-]

> a scheme to allow easy tree traversal

Huh that sounds a lot like graphql

	▲	sgarland 3 days ago \| parent [-]
		GraphQL isn’t changing your schema, it’s issuing queries to satisfy your request. The queries are in no way guaranteed to be optimal, or well-suited for your schema or indices.