3 ms·
GraphQL raison d’être was not to federate and proxy different, heterogeneous data sources. It has initially been developed as a better API for the Facebook mono
by ngrilly 4y ago
GraphQL raison d’être was not to federate and proxy different, heterogeneous data sources. It has initially been developed as a better API for the Facebook monolith. I asked one of GraphQL’s coauthors directly: https://twitter.com/ngrilly/status/1317415232717860866?s=46&t=gYGscP7V495SUtGS61l83g https://twitter.com/ngrilly/status/1317415232717860866?s=46&....
- e12e 4y agoInteresting - I didn't even know that there was a monolith at Facebook [ed: beyond there being reports that they use a large monorepo for code]. I stand corrected, thank you. This doesn't directly address if graphql at Facebook federated different data sources (eg graph and sql databases) - but I suppose not?
- ngrilly 4y agoI don't have any "insider" information regarding the data sources used by the Facebook monolith, written in PHP, when GraphQL has been developed, but I would expect it to talk to multiple/different datastores, and not just MySQL. Then yes, it could be argued that it has been used to federate multiple data stores, even though it was already the case before using GraphQL :)