Live data from Hacker News

Million User Webchat with Full Stack Flux, React, Redis and PostgreSQL

blog.rotenberg.io

31–40 of 41 posts

Re: Million User Webchat with Full Stack Flux, React, Redis and PostgreSQL

#31
AFAICT, Facebook engineered their client side code around Flux in order to eliminate two-way data binding in their user interface code, which leads to all sorts of issues. I don't imagine they push the pattern into the server. Their relay stuff still relies upon a smart data tier which understands a query language called GraphQL.

I definitely don't think they considered implementing a dumb dispatcher and store layer on the database server using stored procedures. (This seems terrifying to me, I don't see the upside.)

It's an interesting experiment but I think this might be an example of being too aggressive in trying to generally apply a design pattern that was motivated by a specific problem.

Re: Million User Webchat with Full Stack Flux, React, Redis and PostgreSQL

#34

GameRanger has six million users, tens of thousands to hundreds of thousands of whom will be active simultaneously. His chat problem involved has moderate fan-out. Scott Kevill does it on a single machine (last time I checked) with hand-rolled C++ and close attention to the details of how the Linux networking stack works.

Single Machine??...really...would love to know more about the stack..

Re: Million User Webchat with Full Stack Flux, React, Redis and PostgreSQL

#35

GameRanger has six million users, tens of thousands to hundreds of thousands of whom will be active simultaneously. His chat problem involved has moderate fan-out. Scott Kevill does it on a single machine (last time I checked) with hand-rolled C++ and close attention to the details of how the Linux networking stack works.

I am also interested to know, Do you've any links on this?

Scott gets very little press -- mostly when he picks up support for games after the publisher or matchmaking service abandons one.

I used to live in Perth and we'd sometimes hang out and mock the front page of HN.

http://www.gameranger.com/about/

Re: Million User Webchat with Full Stack Flux, React, Redis and PostgreSQL

#36
post #27

I suppose there is some value to this as a thought experiment but pretty much every tier in that architecture has breaking flaws. The most relevant being that anything that has an audience of 1 million users cannot run on an architecture that has single points of failure.

Physically the hardware can't handle it or are you just advocating that it shouldn't?

Re: Million User Webchat with Full Stack Flux, React, Redis and PostgreSQL

#38
post #27

I suppose there is some value to this as a thought experiment but pretty much every tier in that architecture has breaking flaws. The most relevant being that anything that has an audience of 1 million users cannot run on an architecture that has single points of failure.

TLDR;'thought experiment', feh, if this was actual tested result would be much more interesting.

Re: Million User Webchat with Full Stack Flux, React, Redis and PostgreSQL

#39
post #27

I suppose there is some value to this as a thought experiment but pretty much every tier in that architecture has breaking flaws. The most relevant being that anything that has an audience of 1 million users cannot run on an architecture that has single points of failure.

TLDR;'thought experiment', feh, if this was actual tested result would be much more interesting.

But if the author didn't "thought experiment" about that, how else would he bait you into clicking...

Re: Million User Webchat with Full Stack Flux, React, Redis and PostgreSQL

#40

The Flux terminology is confusing to me. It looks like the Observer pattern to me. * Stores contain Observables * Components (or Views) contain Observers * Actions are Proxies So the article is basically saying the Observer pattern is scalable, but uses the buzz-phrase "Full Stack Flux" instead. To make it even worse it is only a theoretical application of this pattern.

[deleted]
Post reply on HN