hypernova

It’s funny, this is how we built apps in 2014-era Rails at Airbnb, and by 2015 we were doing server-side rendering of some React components too. We had a thing to pop a React component into our regular rails views as a “partial”. <%= render_react_component('MyComponent.js', :name => 'Hypernova The Renderer') %> https://github.com/airbnb/hypernova?tab=readme-ov-file#rails

it's not quite impossible, there are some more "out there" server-side rendering approaches which would work: - https://github.com/airbnb/hypernova - https://github.com/prerender/prerender Fans of efficiency and simplicity might recoil but if it works and is easy to setup, these far out approaches might just catch.

IIUC you both were just talking past each other? one was talking about SSR to a full hydrated SPA, the other about a MPA with some hydration here and there. I have been doing the latter for some time with https://github.com/airbnb/hypernova for a rails API.

The issue here is nodejs, react ssr is costly, taking all you cpu time, blocking the event loop and slowing down your app. On a multi-threaded (async or sync) web server this wouldn't be a issue most of the time. Some add additional nodejs servers specifically and only for SSR, increasing complexity. airbnb created https://github.com/airbnb/hypernova to solve exactly this problem.

Ah! I see what you mean. It reminds me of https://github.com/airbnb/hypernova

Link: https://github.com/airbnb/hypernova

https://github.com/airbnb/hypernova Personally I find it pretty interesting but could really be benefital for sophisticated frontend apps, thoughts?

All of the skeletons/starting points out there pretty much ignore the fact that backends exist in general (by making demos just github stargazing or whatever, or using firebase/<insert graphqlaas> and such). It's definitely not the case that you need explicit nodejs on the backend, and that's not the common case for a lot of large companies. There are tons of options. Render services [1], Sidecar processes [2], not-doing-universal-rendering, or just running a simple universal nodejs server with an entirely separate API backend. [1]: https://github.com/airbnb/hypernova [2]: https://blogs.msdn.microsoft.com/webdev/2017/02/14/building-... Integration is not typically that difficult. It takes a day or two of sitting down with docs and intentional effort, sure. Worrying about wasted effort is silly though. The amount of choice these days is cr

There are a few approaches, usually via a standalone node.js service. I've seen similar architectures for ruby and python web servers as well. I'm working on a project now that uses airbnb's hypernova service[0] with a php client[1]. Edit: not suggesting this was used in this case, just that it's a viable option for react ssr + php. [0] - https://github.com/airbnb/hypernova [1] - https://github.com/wayfair/hypernova-php

Doesn't avoid the node dependency, but try https://github.com/airbnb/hypernova Honestly the node dep isn't so bad. Just think of it as a template render running on another process.

A lot of smart engineering teams seem to be picking up Node recently. Airbnb and Netflix are two interesting examples. https://github.com/airbnb/hypernova http://thenewstack.io/netflix-uses-node-js-power-user-interf...

What are the server memory consumption numbers for this ? How is this different from Hypernova [0] ? [0] https://github.com/airbnb/hypernova