5 ms·

> 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

> 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”.

cowsandmilk 3y ago
How would vertical integration be related to migrating the iOS and Android apps to using GraphQL?
- pixelatedindex 3y ago
  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.
- thephyber 3y ago
  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.
- thephyber 3y ago
  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/ https://www.infoq.com/presentations/netflix-scaling-graphql/
saurik 3y ago
> 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%. 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 pretty awkward--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 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. Is the claim here that one of these applications on other platforms has new functionality that isn't available on any of the major ones? I mean, I listed AppleTV as I can guarantee the app is both not changing and getting slower, but it isn't like I am not using Netflix on other platforms and it isn't as if I don't know it is also embedded into a ton of random one-off devices... I just don't see what point you are trying to make by expanding the scope here as it feels a bit like an attempt to nitpick rather than educate how I might be wrong here. > Also, they are a company, so they are always looking to be able to optimize and cut costs. I suggested this as an option in my comment. Do you believe this cuts costs? It wasn't at all clear to me that doing all of this work would cut costs, but if you can explain how that would be fascinating. (It, though, sounds like you don't know anything more about this than I do: you are just less skeptical for some reason. If you work for Netflix and would like to publish an article about why this update was a great idea I would totally be the first to read it and applaud the effort, though.) > It’s worth staying curious and asking why before assuming you know more than the engineers who have to work “behind the curtain”. You are literally responding to a comment that begins with "Why?" --one which then continues with a ton of questions that could simply be answered by someone at Netflix if they so cared (and frankly, I will claim, should have been answered in this blog post, as the subject matter begs this question and usually one starts a project postmortem with a comprehensive section on one's motivations)--with a comment trying to establish the moral high ground by... saying I should ask why?
- thephyber 3y ago
  Some of your questions are answered here: https://www.infoq.com/presentations/netflix-scaling-graphql https://www.infoq.com/presentations/netflix-scaling-graphql

cowsandmilk 3y ago

How would vertical integration be related to migrating the iOS and Android apps to using GraphQL?

pixelatedindex 3y ago
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.
thephyber 3y ago
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.
thephyber 3y ago
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/ https://www.infoq.com/presentations/netflix-scaling-graphql/

saurik 3y ago

> 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%. 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 pretty awkward--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 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. Is the claim here that one of these applications on other platforms has new functionality that isn't available on any of the major ones? I mean, I listed AppleTV as I can guarantee the app is both not changing and getting slower, but it isn't like I am not using Netflix on other platforms and it isn't as if I don't know it is also embedded into a ton of random one-off devices... I just don't see what point you are trying to make by expanding the scope here as it feels a bit like an attempt to nitpick rather than educate how I might be wrong here. > Also, they are a company, so they are always looking to be able to optimize and cut costs. I suggested this as an option in my comment. Do you believe this cuts costs? It wasn't at all clear to me that doing all of this work would cut costs, but if you can explain how that would be fascinating. (It, though, sounds like you don't know anything more about this than I do: you are just less skeptical for some reason. If you work for Netflix and would like to publish an article about why this update was a great idea I would totally be the first to read it and applaud the effort, though.) > It’s worth staying curious and asking why before assuming you know more than the engineers who have to work “behind the curtain”. You are literally responding to a comment that begins with "Why?" --one which then continues with a ton of questions that could simply be answered by someone at Netflix if they so cared (and frankly, I will claim, should have been answered in this blog post, as the subject matter begs this question and usually one starts a project postmortem with a comprehensive section on one's motivations)--with a comment trying to establish the moral high ground by... saying I should ask why?

thephyber 3y ago
Some of your questions are answered here: https://www.infoq.com/presentations/netflix-scaling-graphql https://www.infoq.com/presentations/netflix-scaling-graphql