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

React Server

react-server.io

Post reply on HN
Print view View original

51–60 of 143 posts

Re: React Server

#51

Post by davidalber »

hyperpape wrote: post #35
AShedOfTools wrote: post #26

Earlier quoted context omitted.

We had some scaling issues, and have added a couple more hosts to the pool. The errors should be resolved now

Good opening for a question: what kind of servers were you using and how much traffic did it take to give them problems? (In other words, what's the performance of react like on the server?)

gigabo's account has been rate limited, but he wants to say:

"Well... we made it through the first hour or so of HN traffic on a single t2.medium instance in ec2 before we started seeing errors. We're now on three m4.larges with good head room. Not too bad, I think?

We meant to get cloud front set up before we got this sort of traffic, but glad to be surprised with an early bump. :)"

This is me saying this: I think we are thoroughly over-provisioned now for the load we are seeing, but we wanted to avoid any more hiccups while you all are trying to check it out.

Re: React Server

#52

Post by acid__ »

encoderer wrote: post #47

An alternative here is Hypernova by Airbnb.

Correct me if I'm mistaken, but Hypernova has the javascript rendering siloed as a separate service. Which can be really useful in some cases (especially if you want to render React components from a Rails app).

But if you want it all in one place (reduced complexity and overhead), React Server looks pretty promising.

Re: React Server

#53

Post by Bartkusa »

tboyd47 wrote: post #50

Looks fascinating, I will definitely be watching this project in the coming year. Just curious, if it's been successfully running in production for over a year, why is it only being used to serve three pages?

That statistic is out of date; Redfin has built dozens of pages on React-Server by this point.

(Also, just to be clear, we treat all home details pages as a single logical page.)

Re: React Server

#54

Post by bphogan »

kough wrote: post #49
gigabo wrote: post #9

Earlier quoted context omitted.

Yes, definitely agree! We need better tutorials! We need better docs in general. Contributions welcome! :D

I'm totally on board with the "contributions welcome" response from open source maintainers, but when it's the only response to questions about documentation it's pretty off-putting. This is your project, how could you expect a new contributor to add docs without your input? I get that good documentation is hard, and takes time, but if you want your project to succeed I think it's almost mandatory for you to write th…

I have to agree here. There's nobody better to explain how something really works than the person who wrote it. The rest of us are just fumbling around guessing.

As a dev and a creative person, I understand the desire to get something out there. But documentation and tutorials aren't just something that's nice to have. They are your marketing tool, your adoption driver, and the way to create educated advocates for your project. They are as valuable to your project's success as a splashy "getting started" web site is.

Re: React Server

#55

Post by hyperpape »

davidalber wrote: post #51
hyperpape wrote: post #35

Earlier quoted context omitted.

Good opening for a question: what kind of servers were you using and how much traffic did it take to give them problems? (In other words, what's the performance of react like on the server?)

gigabo's account has been rate limited, but he wants to say: "Well... we made it through the first hour or so of HN traffic on a single t2.medium instance in ec2 before we started seeing errors. We're now on three m4.larges with good head room. Not too bad, I think? We meant to get cloud front set up before we got this sort of traffic, but glad to be surprised with an early bump. :)" This is me saying this: I think w…

I honestly don't know, what's the actual requests/second for that?

I don't have a good feel for what HN traffic is like. From one post (https://news.ycombinator.com/item?id=8107658), it seems like a few thousand hits/hour over a fraction of a day, but (1) there's a lot of variation, (2) it doesn't tell you the peak rate

Re: React Server

#57

Post by silasb »

The company that I was consulting for tried to get Spring and React to play nice via Nashorn, but ended up scraping the idea 6 weeks in because of performance issues and not enough developers knowing the stack. Nashorn was missing a lot of essentials to make this easy out of the box. So looking at this is a breath of fresh air.

Re: React Server

#59

Post by trjordan »

kough wrote: post #49
gigabo wrote: post #9

Earlier quoted context omitted.

Yes, definitely agree! We need better tutorials! We need better docs in general. Contributions welcome! :D

I'm totally on board with the "contributions welcome" response from open source maintainers, but when it's the only response to questions about documentation it's pretty off-putting. This is your project, how could you expect a new contributor to add docs without your input? I get that good documentation is hard, and takes time, but if you want your project to succeed I think it's almost mandatory for you to write th…

I don't think that's true. It's certainly possible for somebody else to run with tutorial creation, especially if the project gets attention / exposure before the tutorials are ready.

If the response "Contributions welcome" is generic, it's because the complaint is as well.

Re: React Server

#60

Post by dustingetz »

onewaystreet wrote: post #45
idbehold wrote: post #42

How does it handle fetching data from a path on the same origin? For instance, I only need to fetch('/api/users.json') on a certain page (/users). This means that it can either be hydrated in the initial state when performing a full page load of /users or needs to be fetched (using xhr/fetch) when navigating to that page from another page on the site (which shouldn't require a full page load). So how exactly does the…

It doesn't. The data is included with the rendered page. React uses checksums to tell if it needs to rerender.

I believe React will always re-render, to attach click handlers and the like.
Post reply on HN