Do I need Node.js in the backend?

Do I need #nodeJS as a #backend when I use #reactJS?

  • Like any other frontend library (jQuery, etc), it is happy to be served by any old webserver – Apache, NGINX – or any kind of backend – PHP, Rails, and so on.
  • Lest we lose track of how the Internet works, here’s a diagram to anchor the discussion:

    Since React and Angular are purely client-side libraries made up of JavaScript files, any old HTTP server can send them to users – PHP inside Apache, PHP inside Nginx, plain Apache/Nginx, Java Tomcat, Rails inside Passenger, and yes, Node.js.

  • I said that React doesn’t care what your server is doing, which is true…

    But if you add React Router to your project, and you want to use its feature, the server must serve up your page no matter which URL the user accesses.

  • Though if your backend is not Node.js, you’ll probably want the last step of your build to be “copy the built files to my server’s root directory.”
  • Alternatively, you could set up Webpack to serve your React app and then proxy all other requests to your real backend server (whether that’s local, or across the web somewhere).

Can you use React with a PHP, Java, Rails, or other kind of backend?
Continue reading “Do I need Node.js in the backend?”

Do I need Node.js in the backend? – Angularity

Do you need Node.js in the backend?  #ReactJS

  • You can use any frontend library for fetching data – React doesn’t come with one.
  • My site is hosted on a PHP/MySQL backend and I read somewhere that I need to have a Node.js environment in the backend to use these new JavaScript libraries like React and Angular 2.
  • Read on for how to fetch data, deal with routing, and server-side rendering without Node.js.
  • If you want to support server-side rendering (a.k.a. “isomorphic” rendering), whether to increase page load speed or to improve SEO, then React will actually be running on both the server and in the browser: once to render the page server-side, and then again in the browser after it downloads and displays the initial rendering.
  • Server-side rendering is way outside the scope of this post, but even if you do need it, you don’t have to use Node.js in the backend.

Read the full article, click here.


@ReactiveConf: “Do you need Node.js in the backend? #ReactJS”


Can you use React with a PHP, Java, Rails, or other kind of backend?


Do I need Node.js in the backend? – Angularity

Announcing Reactive Trader Cloud

  • Announcing Reactive Trader Cloud
  • Reactive Trader Cloud is a demo client-server FX trading application.
  • To launch Reactive Trader in our demo environment, click .
  • The backend is composed of a set of services which can be scaled, deployed and upgraded independently.
  • Instead of using HTTP, the client connects to the backend using Websockets and since we have a number of services, we decided to use a messaging gateway to act as a broker: this allows the client to establish a single connection to the backend and the broker is used to route messages to the correct service instance or to the correct client.

Read the full article, click here.


@AdaptiveLimited: “Reactive Trader Cloud released, #reactjs front-end, backend on #Kubernetes, all open source!”


In April 2014 we gave a talk at React Conf London on Reactive user interfaces and open-sourced Reactive Trader, a demo app we used to demonstrate the different concepts we highlighted in the talk. The talk was focused on UIs so we put most of our effort into the front-end and built a very simple monolithic backend to simulate the different flows and failure scenarios.


Announcing Reactive Trader Cloud