Think back to other query languages we've used, ... say SQL?
Yes, there is enormous power and flexibility in query languages. But does anyone remember the pain of tuning these queries? This power and flexibility comes at a cost.
I'd be curious to know how much effort Facebook spent behind the scenes tuning (or building a query optimizer) over the last 4+ years. And each company's services and databases will force a separate tuning effort. Facebook's tuning efforts probably can't be translated to other non-social-network use cases.
Sorry to be a bummer. I agree that GraphQL is incredible, but like that old saying: "If it sounds too good to be true, it probably is." :-/
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Think back to other query languages we've used, ... say SQL?
Yes, there is enormous power and flexibility in query languages. But does anyone remember the pain of tuning these queries? This power and flexibility comes at a cost.
I'd be curious to know how much effort Facebook spent behind the scenes tuning (or building a query optimizer) over the last 4+ years. And each company's services and databases will force a separate tuning effort. Facebook's tuning efforts probably can't be translated to other non-social-network use cases.
Sorry to be a bummer. I agree that GraphQL is incredible, but like that old saying: "If it sounds too good to be true, it probably is." :-/