I had a hard time figuring out what this is. But looking at the justification fb wrote about graphql: https://code.facebook.com/posts/1691455094417024/graphql-

I had a hard time figuring out what this is. But looking at the justification fb wrote about graphql: https://code.facebook.com/posts/1691455094417024/graphql-a-data-query-language/ https://code.facebook.com/posts/1691455094417024/graphql-a-d... It would appear it's a half-assed string-based, semi-structured ddl / query-language aiming to be a middleware between actual data storage and thin clients, presenting legacy data as a graph (rather than, say, a (filesystem-like) tree or a relational table structure). Surprisingly the responses are json while the queries, as far as I can tell, cannot be parsed as js/json - but look very similar. Based on that, I gather this is firebase with a graphql front-end: a db-as-a-service with no clear path to move off of if needed? (compared to, say, sql-server as a service). Perhaps harsh, but at least put like that I think both the value-proposition and trade-off is more obvious? Assuming I understood it correctly, of course. Corrections welcome.