How Netflix Really Uses Java

Re:How Netflix Really Uses Java by jarym on Tuesday October 10, 2023 @04:11AM (#37829633)

Interesting the article jumps straight from REST to GraphQL and forgets Falcor[0] - Netflix's alternative vision for federated services. For a while it looked like it might be a contender to GraphQL but it never really seemed to take off despite being simpler to adopt.

[0] https://netflix.github.io/falcor/

[ Parent | on HN ]

Re:How Netflix Really Uses Java by lfkdev on Tuesday October 10, 2023 @05:37AM (#37830080)

`Sad Prime noises`

[ Parent | on HN ]

Re:How Netflix Really Uses Java by dustingetz on Tuesday October 10, 2023 @06:23AM (#37830340)

iirc falcor predated graphql

[ Parent | on HN ]

Re:How Netflix Really Uses Java by ppseafield on Tuesday October 10, 2023 @12:35PM (#37834322)

I was at the React Rally conference where Falcon was publcly announced in August of 2015. I recall that Facebook gave a GraphQL presentation right before.

It seems GraphQL was first announced publicly in February 2015.

[ Parent | on HN ]

Re:How Netflix Really Uses Java by parthdesai on Tuesday October 10, 2023 @10:03AM (#37832247)

Netflix themselves have moved off falcor though

https://netflixtechblog.com/migrating-netflix-to-graphql-saf...

[ Parent | on HN ]

Re:How Netflix Really Uses Java by paulbakker on Tuesday October 10, 2023 @12:33PM (#37834296)

Falcor is actually part of the "old" architecture described in the talk. Because it's mostly unknown and no longer used I didn't go into the details of it.

Falcor was developed at the time Facebook was developing GraphQL in-house. It has similar concepts, but never took off the way GraphQL did.

[ Parent | on HN ]

Re:How Netflix Really Uses Java by baby on Tuesday October 10, 2023 @04:53PM (#37837302)

Probably because most people don't want to work with Java

[ Parent | on HN ]