News for hackers. Stuff that matters.
Re:Migrating Netflix to GraphQL Safely by thephyber on Sunday June 18, 2023 @05:09PM (#36384512)
> isn't the app "done"?

Netflix is an ecosystem, not just the frontend app for Apple TV. Netflix is pretty close to a vertical monopoly for some of its content. Fund-raising, planning, development, post-production, translations/dubbing, preparation for distribution, and distribution. Your idea of viewing a video content on the app is only the last 20%.

Also worth reminding people that the AppleTV app is not the only app Netflix supports for viewing. There have been dozens/hundreds of different apps and most are still actively supported.

Also, they are a company, so they are always looking to be able to optimize and cut costs.

It’s worth staying curious and asking why before assuming you know more than the engineers who have to work “behind the curtain”.

Re:Migrating Netflix to GraphQL Safely by cowsandmilk on Sunday June 18, 2023 @08:18PM (#36385887)
How would vertical integration be related to migrating the iOS and Android apps to using GraphQL?
Re:Migrating Netflix to GraphQL Safely by pixelatedindex on Sunday June 18, 2023 @09:01PM (#36386105)
I’m no expert, but as I understand it, the clients have more flexibility to request things from the backend. I don’t know the app source code, but maybe it reduces complexity in app design?

Would love to hear other opinions.

Re:Migrating Netflix to GraphQL Safely by thephyber on Monday June 19, 2023 @07:38PM (#36397817)
If their dev team believes there is value in GraphQL, maybe they also want those same benefits for their business apps/APIs in addition to their customer-facing ones. Maybe they all use the same API gateway.
Re:Migrating Netflix to GraphQL Safely by thephyber on Wednesday June 21, 2023 @04:36AM (#36415970)
Scroll to 7:47 in this presentation[1] and see that the different domains within the Netflix vertical are all part of the same large API, accessible from the same API gateway.

People here are making an assumption that the entrypoint to Netflix's microservice ecosystem is only for the "TV App". No -- their other domains (incl. talent and production) also depend on the same API gateway. When they upgrade the API gateway to GraphQL for one app and you might as well do it for all apps to get the benefits of the GraphQL toolset.

[1] https://www.infoq.com/presentations/netflix-scaling-graphql/

Re:Migrating Netflix to GraphQL Safely by saurik on Monday June 19, 2023 @02:39AM (#36388002)
Ok, so you are saying this GraphQL API is also being used by numerous integrations behind the scenes that are--in your estimation, as I find this idea categorically absurd--managing the fund-raising, planning, development, post-production, etc. of the numerous random production houses that are working on projects for Netflix all somehow within Netflix's central database?

> Also, they are a company, so they are always looking to be able to optimize and cut costs.

I suggested this as an option. Do you believe this cuts costs?

Re:Migrating Netflix to GraphQL Safely by thephyber on Monday June 19, 2023 @07:48PM (#36397898)
Some of your questions are answered here:

https://www.infoq.com/presentations/netflix-scaling-graphql