←back to thread

492 points storf45 | 1 comments | | HN request time: 0s | source
Show context
shermantanktop ◴[] No.42160502[source]
Every time a big company screws up, there are two highly informed sets of people who are guaranteed to be lurking, but rarely post, in a thread like this:

1) those directly involved with the incident, or employees of the same company. They have too much to lose by circumventing the PR machine.

2) people at similar companies who operate similar systems with similar scale and risks. Those people know how hard this is and aren’t likely to publicly flog someone doing their same job based on uninformed speculation. They know their own systems are Byzantine and don’t look like what random onlookers think it would look like.

So that leaves the rest, who offer insights based on how stuff works at a small scale, or better yet, pronouncements rooted in “first principles.”

replies(15): >>42160568 #>>42160576 #>>42160579 #>>42160888 #>>42160913 #>>42161148 #>>42161164 #>>42161399 #>>42161529 #>>42161703 #>>42161724 #>>42161889 #>>42165352 #>>42166894 #>>42167814 #
dpkirchner ◴[] No.42160576[source]
Right? A common complaint by outsiders is that Netflix uses microservices. I'd love to hear exactly how a monolith application is guaranteed to perform better, with details. What is the magic difference that would have ensured the live stream would have been successful?
replies(3): >>42160625 #>>42160650 #>>42161427 #
ilrwbwrkhv ◴[] No.42161427[source]
I am one of the ones who complain about their microservices architecture quite a lot.

This comes from both first-hand experience of talking to several of their directors when consulted upon on how to make certain systems of theirs better.

It's not just a matter of guarantees, it's a matter of complexity.

Like right now Google search is dying and there's nothing that they can do to fix it because they have given up control.

The same thing happened with Netflix where they wanted to push too hard to be a tech company and have their tech blogs filled with interesting things.

On the back end they went too deep on the microservices complexity. And on the front end for a long time they suffered with their whole RxJS problem.

So it's not an objective matter of what's better. It's more cultural problem at Netflix. Plus the fact that they want to be associated with "Faang" and yet their product is not really technology based.

replies(5): >>42161613 #>>42161627 #>>42161996 #>>42162297 #>>42166261 #
kjellsbells ◴[] No.42161613[source]
> they want to be associated with "Faang" and yet their product is not really technology based.

You lost me. Netflix built a massive CDN, a recommendation engine, did dynamic transcoding of video, and a bunch of other things, at scale, quite some years before everyone else. They may have enshittified in the last five years, but I dont see any reason why they dont have a genuinely legitimate claim to being a founder member of the FAANG club.

I have a much harder time believing that companies with AI in their name or domain are doing any kind of AI, by contrast.

replies(2): >>42162442 #>>42163584 #
badpun ◴[] No.42163584[source]
Same thing was done a little later by HBO, Disney and a plethora of others, which points to the task not really being uber-difficult.
replies(2): >>42164110 #>>42164213 #
moomin ◴[] No.42164110{3}[source]
Speaking as a consumer, Netflix’s solution is objectively better than it’s competitors. It handles network blips better, it’s more responsive to use, it has far fewer random bugs you need to work around.

You can argue whether or not that edge translates into more revenue, but the edge is objectively there.

replies(2): >>42166932 #>>42172878 #
1. IIsi50MHz ◴[] No.42172878{4}[source]
Agree. Hulu, HBO/Max, and Disney Plus each do most of these:

- frequently decide that episodes I've watched are either completely unwatched (with random fully watched eps of the show mixed in).

- seemingly every time I leave at the start of the end-credits, I surely must have intended to come back and watch them.

- rebuild the entire interface (progressively, slowly) when I've left the tab unfocussed for too long. Instead of letting continue where I was, they show it for less than a second, the rebuild the world.

- keep resetting the closed-caption setting to "none", regardless of choosing "always" or "on instant replay"; worse, they sometimes still have the correct setting in the interface, but have disabled captions anyway.

Netflix has only once since they started streaming forgotten playback position or episode completion. They politely suggest when to reload the page (via a tiny footer banner), but even that might not appear for months. They usually know where end-credits really start, and count that as completion. They don't seem to mess with captions.