Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

How Netflix really uses Java

infoq.com

Post reply on HN
Print view View original

51–60 of 100 posts

Re: How Netflix really uses Java

#51

Post by John23832 »

CharlieDigital wrote: post #33
Nican wrote: post #27

I have been out of the loop with Java. Is Virtual Threads the answer to asynchronous I/O? (Much like Go/C# async/node.js?) That looks like an interesting solution to support asynchronous I/O without breaking all the APIs, and having the async/await mess that C# created.

> ...the async/await mess that C# created What do you find messy about it? Seems fairly straight forward, IME.

Agreed. The task system in C# is pretty clean imo. Same with Rust (sans the type system implementation of Futures) and Go's goroutines. Especially compared to CompletableFuture in Java.

Re: How Netflix really uses Java

#52

Post by sgt »

jshen wrote: post #39
shp0ngle wrote: post #36

Earlier quoted context omitted.

I don't think the experience is that much different between the different services, honestly. I vaguely have some recollection of Max being a bit bad, but don't remember the details. They are all fine. Except for YouTube, that's just leagues ahead of everything else.

the tvos app for youtube is pretty bad

What problems are you experiencing?

Re: How Netflix really uses Java

#53

Post by grepfru_it »

breakfastduck wrote: post #40
shp0ngle wrote: post #36

Earlier quoted context omitted.

I don't think the experience is that much different between the different services, honestly. I vaguely have some recollection of Max being a bit bad, but don't remember the details. They are all fine. Except for YouTube, that's just leagues ahead of everything else.

Nah the Disney app is really poor, it crashes / refuses to load way more than the other ones in my experience. On multiple different devices / networks.

This adds absolutely nothing to the conversation, but the Disney app on LG tvs are rock solid

Re: How Netflix really uses Java

#54

Post by fzeindl »

schainks wrote: post #19
iammiles wrote: post #4

…let's say, your TV, or your iOS device will just do 10 network calls to these different microservices. It will just not scale at all. You would have a very bad customer experience. It would feel like using the Disney app. It's just not ideal. That’s some shade.

Lol the Disney+ app UX is honestly terrible. Not to mention the regular app crashes on apple devices. Disney has _how_ much money to spend on their streaming services technology stack and they just... don't? Just feels like they'll piss on the customerwhen given the chance because people will still pay for that sweet Disney juice regardless.

What I find funny is that with that kind of money you could staff 10 app teams, develop the app 10 times in different ways and just pick the best one in the end.

Re: How Netflix really uses Java

#56

Post by grepfru_it »

mtlmtlmtlmtl wrote: post #25

This is mostly off-topic I suppose but I recently noticed that Netflix, and Netflix on my TV(WebOS) specifically is absolutely spamming my router with DNS requests sometimes several times a minute, most of them for nrdp-ipv6.prod.ftl.netflix.com. I'm not blocking them btw, so it's not some buggy retry thing going on. Even if I do a hard reboot of my TV and don't start the app, my TV is still happily resolving away. I…

It looks like the TTL on that address is 24 hours, so likely a problem of the dns resolver, which would point to webos. Have you tried a factory reset recently? (Or root and diagnose the system internally)

Re: How Netflix really uses Java

#57

Post by mattmanser »

shp0ngle wrote: post #36
iammiles wrote: post #4

…let's say, your TV, or your iOS device will just do 10 network calls to these different microservices. It will just not scale at all. You would have a very bad customer experience. It would feel like using the Disney app. It's just not ideal. That’s some shade.

I don't think the experience is that much different between the different services, honestly. I vaguely have some recollection of Max being a bit bad, but don't remember the details. They are all fine. Except for YouTube, that's just leagues ahead of everything else.

I don't feel that's true.

For example, Disney is actually pretty terrible compared to Netflix + Prime. Worst part of the service is when it frequently loses where you were in a program. They also made it really hard to get to 'continue watching' for a long time.

Another one that has annoying UX issues is BBC iPlayer. If you click on the latest episode of a show that you're watching in 'popular', it won't resume where you were in the episodes, it will play that episode. Very frustrating. While technically correct, that's not what most people want to happen.

Re: How Netflix really uses Java

#58

Post by NavinF »

bcrosby95 wrote: post #42
shp0ngle wrote: post #36

Earlier quoted context omitted.

I don't think the experience is that much different between the different services, honestly. I vaguely have some recollection of Max being a bit bad, but don't remember the details. They are all fine. Except for YouTube, that's just leagues ahead of everything else.

YouTube is the only thing I've ever interacted with where I can hear the audio of videos that I shouldn't be able to hear. And I've had times where two were playing at once overlapping eachother. It only happens a few times per year for me, but I've never had it happen on another service.

Small price to pay for videos that load almost instantly. It's certainly faster than my Jellyfin setup despite Jellyfin's massive home field advantage (SSDs and 0ms LAN latency)

Re: How Netflix really uses Java

#59

Post by Analemma_ »

geodel wrote: post #44

[flagged]

I mean, I upvoted the story because Netflix is pretty well-known for being a high-intensity dev environment where people are regularly PIP'd and dismissed if their engineering output doesn't measure up - of all the companies which do the eye-rolling claim of "we only hire 10x engineers", Netflix is one of the only ones for which it kinda holds water. And yet, despite this, their stack is boring old Java+Spring. That seems like a useful lesson for all the people who demand that high-performance teams must use the New Shiny.

Re: How Netflix really uses Java

#60

Post by mtlmtlmtlmtl »

grepfru_it wrote: post #56
mtlmtlmtlmtl wrote: post #25

This is mostly off-topic I suppose but I recently noticed that Netflix, and Netflix on my TV(WebOS) specifically is absolutely spamming my router with DNS requests sometimes several times a minute, most of them for nrdp-ipv6.prod.ftl.netflix.com. I'm not blocking them btw, so it's not some buggy retry thing going on. Even if I do a hard reboot of my TV and don't start the app, my TV is still happily resolving away. I…

It looks like the TTL on that address is 24 hours, so likely a problem of the dns resolver, which would point to webos. Have you tried a factory reset recently? (Or root and diagnose the system internally)

My system is rooted actually, but no idea how to disgnose this. I can SSH in but it's a very limited busybox setup and everything app-related seems to be encrypted.
Post reply on HN