Early on (15+ years ago) I spent a few weeks there on contract and I noticed they used Java EVERYWHERE, and not always well. They had a CS app named after a key Star Wars character that was in all likelihood a breach of the Geneva Convention. A code atrocity with the performance of a sloth on its 8th bong rip with a UX from hell.
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.<p>[0] <a href="https://netflix.github.io/falcor/" rel="nofollow noreferrer">https://netflix.github.io/falcor/</a>
>Netflix observed a 20% increase of CPU usage on JDK 17 compared to JDK 8. This was mostly due to the improvements in the G1 garbage collector.<p>Help me here, why do GC improvements cause CPU increase?
Most of the postings for backend positions at Netflix I've seen call out nodejs. Can I assume they do both? Is one legacy and the other newer stuff, or are they more complimentary?<p>Anyone on in the inside know?
Is this the talk? Looks like this is it <a href="https://www.youtube.com/watch?v=5dpLVvRpPPs">https://www.youtube.com/watch?v=5dpLVvRpPPs</a>
Netflix’s DGS framework for GraphQL is nice to work with but we’ve been frustrated with some prioritization choices by the team. For instance, if you’re using Kotlin, it’s impossible to define and pass scalars to the latest version of the client. There’s a year-old issue highlighting this problem that’s been ignored it seems.<p><a href="https://github.com/Netflix/dgs-codegen/issues/455">https://github.com/Netflix/dgs-codegen/issues/455</a>
This seems entirely unsurprising/standard Java setup. Perhaps it is proximity to Hollywood that some glamor is rubbed off on bog standard enterprise tech stack of Netflix.
It seems that this article should be titled "How Netflix uses JVM" (not "Java").<p>The article is superficial, mentions Java but seems that Groovy had a more important role there. But in the end, it really talks about JVM.<p>It reads like a PR piece from a Oracle and Netflix partnership to promote Java. Oracle have done that before.
Not surprised about Rx. Rx is great at the UI layer imho, or anything with streams. For microservices, I don't see how it would have ever fit, since microservices should be as simple as possible doing just one thing.
When they say "applications" do they mean stuff with more meat than microservices? If they're mostly microservices, 2800 seems low to me for someone with the recognition factor of Netflix.
Ah, the way they break out artwork calls explains the weird behaviour I see with my U.K. Netflix account in Portugal - English titles, Portuguese posters, regardless of language preferences.