34 comments

[ 5.0 ms ] story [ 95.0 ms ] thread
Seems stupid to call it flux
Surely it's because it looks like a flux capacitor. Seems reasonable to me.
They should have called it Uterus.
I came here just to confirm that someone would complain about the name.
Especially since Netflix is using React pretty heavily- they must know that there's a conflict.
React is tangible and an actual product; FB's flux is a cute name for a very fuzzy concept.
Well, Flux is a library as well, and it's pretty well understood. Not sure what's fuzzy about it.
(comment deleted)
For those reading comments first and hoping a title like this means Netflix is finally doing something decent in the way suggestions and not showing the same move/show on multiple sliders on the same page. I.e. it's now got better intuition.. you'll be disappointed.

If your looking for really fancy Netflix network infrastructure stuff, dive right in! They are great at this stuff :-D

It's pretty amazing that the traffic was nearly entirely redirected in 20 seconds and then whatever issue that was plaguing the server was resolved so quickly.
Is it just me or has the Netflix engineering team really been cranking out good stuff as of recent times? I mean holy crap. This thing feels so futuristic just watching it. I can't begin to express how blown away I am.

Given how crazy creative the netflix team is, it's not a stretch to imagine their next hackathon. Put this on a big screen and sit in front of it. Throw in a few hazard lights and a siren and music that plays automatically the moment there's a failure and it's a done deal.

Side note: If you want to get a better understanding of what you are reading, the inline linked article[1] is a must read

Also, I actually thought the pain suit was a real thing for a moment. Well played Netflix. Well played.

[1]http://techblog.netflix.com/2015/09/chaos-engineering-upgrad...

I want this NOW. Anyone know if they are planning on open-sourcing this project?
I'd be surprised if they did. This seems pretty specific to their kind of high volume traffic business. And to their distributed nature of data and latency management etc. Not sure how applicable it will be to other businesses.

That said, since it is at its core a logging tool of sorts, it's possible that it's decoupled enough to put it out. But that's really stretching it.

Uh...you realize the visualization is probably the easiest part of this tool? Getting realtime insight into your network is the much harder problem, and you will need to implement that all yourself.
Unless you're starting from the ground up...
and yet, they cannot come up with a creative name
Funny you say that. JSX existed as a language that compiles to javascript before Facebook choosed to use that name :

https://github.com/jsx/JSX

and don't get me started on flux,relay or graphQL ...

And even before that Firefox supported a different JSX which also let you embed xml in JS. Looks like they removed it some time ago...
I think you are talking about e4x. It is really too bad it didn't end up in the spec.
choosed -> chose
Yeah, I always had hard time with this verb, excuse my french.
cool! but they couldn't have thought of a different name?
Nice! A few years ago I made a little program like this, called packet flight, to visualize network flows. It's a nice way to see the magic:

https://vimeo.com/17248120