News for hackers. Stuff that matters.
Re:We Built a Self-Healing System to Survive a Concurrency B... by TZubiri on Wednesday November 13, 2024 @10:19AM (#42126775)
Netflix is supposed to be the bastion of microservices and the trailblazer of all-aws infrastructure.

But as time goes by I just ask, all this work and costs and complexity, to serve files? Yeah don't get me wrong, the size of the files are really big, AND they are streamed, noted. But it's not the programming complexity challenge that one would expect, almost all of the complexity seems to stem from metadata like when users stop watching, and how to recommend them titles to keep them hooked, and when to cut the titles and autoplay the next video to make them addicted to binge watching.

Case in point, the blogpost speaks of a CPU concurrency bug and clients being servers? But never once refers to an actual business domain purpose. Like are these servers even loading video content? My bet is they are more on the optimizing engagement side of things. And I make this bet knowing that these are servers with high video-like load, but I'm confident that these guys are juggling 10TB/s of mouse metadata into some ML system more than I'm confident that they have some problem with the core of their technology which has worked since launch.

As I say this, I know I'm probably wrong, surely the production issues are cause by high peak loads like a new chapter of the latest series or whatever.

I'm all over the place, I just don't like netflix is what I'm saying

Re:We Built a Self-Healing System to Survive a Concurrency B... by bobdvb on Wednesday November 13, 2024 @12:13PM (#42127930)
Netflix has done massive amounts of work on BSD to improve it's network throughput, that's part of them enabling their file delivery from their CDN appliances. https://people.freebsd.org/~gallatin/talks/euro2022.pdf

They've also contributed significantly to open source tools for video processing, one of the biggest things that stands out is probably their VMAF tool for quantifying perceptual quality in video. It's probably the best open source tool for measuring video quality out there right now.

It's also absolutely true that in any streaming service, the orchestration, account management, billing and catalogue components are waaaay more complex than actually delivering video on-demand. To counter one thing you've said: mouse movement... most viewing of premium content isn't done on web or even mobile devices. Most viewing time of paid content is done on a TV, where you're not measuring focus. But that's just a piece of trivia.

As you said, you just don't like them, but they've done a lot for the open source community and that should be understood.

Re:We Built a Self-Healing System to Survive a Concurrency B... by TZubiri on Wednesday November 13, 2024 @08:48PM (#42132320)
Yeah I stand corrected. Video being one of the highest entropy types of data probably means they face state of the art throughput challenges. Which are inherently tied to cost and monetization.

That said, free apps like tiktok and youtube probably face higher throughput, so the user-pays model probably means netflix is at the state of the art at high volume quality (both app experience and content) rather than sheer volume low quality or premium quality low volume markets.

I mean serving millions of customers at 8 bucks per month. Which is not quite like serving billions.

Re:We Built a Self-Healing System to Survive a Concurrency B... by toast0 on Wednesday November 13, 2024 @11:25AM (#42127429)
> But as time goes by I just ask, all this work and costs and complexity, to serve files?

IMHO, a large amount of the complexity is all the other stuff. Account information, browsing movies, recommendations, viewed/not/how much seen, steering to local CDN nodes, DRM stuff, etc.

The file servers have a lot less complexity; copy content to CDN nodes, send the client to the right node for the content, serve 400Gbps+ per node. Probably some really interesting stuff for their real time streams (but I haven't seen a blog/presentation on those)

Transcoding is probably interesting too. Managing job queues isn't new, but there's probably some fun stuff around cost effectiveness.

Re:We Built a Self-Healing System to Survive a Concurrency B... by PittleyDunkin on Wednesday November 13, 2024 @10:34AM (#42126909)
> But as time goes by I just ask, all this work and costs and complexity, to serve files?

You could say the same thing about the entire web.

Re:We Built a Self-Healing System to Survive a Concurrency B... by nicce on Wednesday November 13, 2024 @10:45AM (#42127021)
Not really. People are not posting data into Netlix. Netflix is mostly read-only. That is huge complexity reducer.
Re:We Built a Self-Healing System to Survive a Concurrency B... by jacksontheel on Wednesday November 13, 2024 @12:09PM (#42127888)
Every time you like/dislike/watchlist a movie you're posting data. When you're watching a movie your progress is constantly updated, posting data. Simple stuff but there's possibly hundreds of thousands of concurrent users doing that at any given moment.
Re:We Built a Self-Healing System to Survive a Concurrency B... by nicce on Wednesday November 13, 2024 @12:18PM (#42127977)
Yes, but it is still counts only a fraction of the purpose of their infrastructure. There are no hard global real-time sync requirements.

> When you're watching a movie your progress is constantly updated, posting data

This can be implemented on server side and with read requests only.

A proper comparison would be YouTube where people upload videos and comment stuff in real-time.

Re:We Built a Self-Healing System to Survive a Concurrency B... by PittleyDunkin on Wednesday November 13, 2024 @02:15PM (#42128960)
> A proper comparison would be YouTube where people upload videos and comment stuff in real-time.

Even in this one sentence you're conflating two types of interaction. Surely downloading videos is yet a third, and possibly the rest of the assets on the site a fourth.

Why not just say the exact problem you think is worth of discussion with your full chest if you so clearly have one in mind?

Re:We Built a Self-Healing System to Survive a Concurrency B... by TZubiri on Wednesday November 13, 2024 @08:56PM (#42132367)
I'd make a distinction on:

-the entropy of the data: a video is orders of magnitude than browsing metadata.

- the compute required: other than an ML algorithm optimizing for engagement, there's no computationally intensive business domain work (throughput related challenges dont count)

- finally programming complexity, in terms of business domain, is not there.

I mean my main argument is that a video provider is a simple business requirement. Sure you can make something simple at huge scale and that is a challenge. Granted.

Re:We Built a Self-Healing System to Survive a Concurrency B... by TZubiri on Wednesday November 13, 2024 @09:05PM (#42132412)
There's many cases where server side takes you 98% there, but it still makes economical sense to spend shitloads on getting that 2% there.

In this case it's not the same whether your server sends a 10 second packet and the viewer views all of it, and whether server sends a 10 second packet, but client pauses at the 5s mark (which needs client-side logic)

Might sound trivial, but at netflix scale there's guaranteed a developer dedicated to that, probably a team, and maybe even a department.

Re:We Built a Self-Healing System to Survive a Concurrency B... by TZubiri on Wednesday November 13, 2024 @10:54AM (#42127116)
I thought about the complexity in terms of compute, but I guess if there's no input then there's no compute possible, as all functions are idempotent and static. At the very least their results are cacheable, or the input is centralized (admins/show producers)
Re:We Built a Self-Healing System to Survive a Concurrency B... by PittleyDunkin on Wednesday November 13, 2024 @02:14PM (#42128951)
Is it? It's pretty rare to download assets from servers that you're uploading to. Sometimes you have truly interactive app servers but that's a pretty small percentage of web traffic. Shared state is not the typical problem to solve on the internet, though it is a popular one to discuss.
Re:We Built a Self-Healing System to Survive a Concurrency B... by nicce on Wednesday November 13, 2024 @02:27PM (#42129069)
Whatever your service is, usually the database is the bottleneck. The database limits the latency, scaling and availability.

Of course, how much, depends on the service. Particularly, how much concurrent writing is happening, and do you need to update this state globally, in real-time as result of this writing. Also, is local caching happening and do you need to invalidate the cache as well as a result of this writing.

The most of the relevant problems disappear, if you can just replicate most of the data without worrying that someone is updating it, and you also don't have cache invalidation issues. No race conditions. No real-time replication issues.

Re:We Built a Self-Healing System to Survive a Concurrency B... by PittleyDunkin on Wednesday November 13, 2024 @02:40PM (#42129170)
> Whatever your service is, usually the database is the bottleneck. The database limits the latency, scaling and availability.

Database-driven traffic is still a tiny percentage of internet traffic. It's harder to tell these days with encryption but on any given page-load on any project I've worked on, most of the traffic is in assets, not application data.

Now, latency might be a different issue, but it seems ridiculous to me to consider "downloading a file" to be a niche concern—it's just that most people offload that concern to other people.

Re:We Built a Self-Healing System to Survive a Concurrency B... by tommygpt on Wednesday November 13, 2024 @02:45PM (#42129203)
Hello sir Mr pittleydunkin Let talk privately About business
Re:We Built a Self-Healing System to Survive a Concurrency B... by nicce on Wednesday November 13, 2024 @05:53PM (#42131114)
> It's harder to tell these days with encryption but on any given page-load on any project I've worked on, most of the traffic is in assets, not application data.

Yet you have to design the whole infrastructure to note that tiny margin to work flawlessly, because otherwise the service usually is not driving its purpose.

Read-only assets are the easy part, which was my original claim.

Re:We Built a Self-Healing System to Survive a Concurrency B... by PittleyDunkin on Wednesday November 13, 2024 @10:05PM (#42132731)
> Read-only assets are the easy part, which was my original claim.

I don't think this is true at all given the volume. With that kind of scale everything is hard. It's just a different sort of hard than contended resources. Hell, even that is as "easy" these days with CRDTs (and I say this with dripping sarcasm).

Re:We Built a Self-Healing System to Survive a Concurrency B... by nicce on Thursday November 14, 2024 @02:38PM (#42140264)
Asset volume is just a price issue in these days. You can reduce the price by using clever caching, with programming language choices, or higher compression rate.. but in the end it is not a real problem anymore in the overall infrastructure architecture. Read-only assets can be copied, duplicated, cached without any worries that they might need to be re-synced soon.
Re:We Built a Self-Healing System to Survive a Concurrency B... by tommygpt on Wednesday November 13, 2024 @02:42PM (#42129180)
Hey! Can we have a business together Am a genius engineer
Re:We Built a Self-Healing System to Survive a Concurrency B... by TZubiri on Wednesday November 13, 2024 @08:51PM (#42132337)
That's true as the internet becomes more $ focused, companies become more interested in shoving messages (ads/propaganda) than letting users say anything). Even isp plans have asymmetric specs.

I'm honestly much more impressed by free apps like youtube and tiktok in terms of throughput, they have MUCH more traffic since users don't pay!

[dead]
Re:We Built a Self-Healing System to Survive a Concurrency B... by TZubiri on Wednesday November 13, 2024 @10:53AM (#42127093)
Rizz skibidi bro