Migrating Netflix to GraphQL safely
I never understood why people go for graphql.<p>In my experience, it&#x27;s a nightmare to 1&#x2F; secure 2&#x2F; version 3&#x2F; ensure qos<p>Securing it properly should make it a no-go in like 95% of cases. you get amazing flexibility on the front end with a heavy heavy cost on the backend. Also, in general being able to say &quot;i want to do whatever&quot; and request everything at once is an anti-pattern IMHO, especially after HTTP2 became mainstream and doing multiple requests is reasonably fast.<p>Versioning? Forget about it. Now you have &quot;all the versions&quot; and good luck figuring out what is used, what is not used or god forbid deprecate something. you&#x27;re going to have a bad time.<p>As far as qos goes, if any client can range from &quot;i&#x27;m asking a simple thing&quot; to &quot;i would like the whole world please - and btw you&#x27;re only going to figure things out as you pull them in&quot; qos becomes a pipe dream.<p>Last, I don&#x27;t understand what Netflix does that is so complex that would warrant something like gql. I just don&#x27;t. To the naive developer in me it seems that they 1) need to have a basic api to get whatever catalog they have + a few apps build on top of that 2) have figured out how to do streaming exceptionally well in order to scale to all the people watching. That&#x27;s is and although a gross oversimplification I cannot think about a scenario where gql is needed.<p>I think in their desire to reinvent the wheel Netflix has jumped the shark. A lot of really good ideas have come out of the innovation they did in the past but lately it seems like they are doing things for the sake of doing them or they are pissing people off with password household policies and whatnot.