Server-Side Rendering Using WebAssembly

Rate this content

This talk shares how to achieve Server-side rendering using WebAssembly and WASMEdge which is a WebAssembly Runtime. The talk also covers the benefits of using WebAssembly to achieve Server Side Rendering. The talk will also cover a demo on how to launch a React application using the WasmEdge runtime.

12 min
24 Oct, 2022

AI Generated Video Summary

Shivai Lamba presents server-side rendering using WebAssembly. Learn how to enable server-side rendering with WebAssembly using a Create React app. See the changes in the app before and after enabling server-side rendering. Support for React 18 and the ability to create streaming applications using WebAssembly. Connect with me on Twitter at TheCloudWeb for more information on WebAssembly.

1. Server-side Rendering with WebAssembly

Short description:

Shivai Lamba presents server-side rendering using WebAssembly. WebAssembly is an efficient, low-level bytecode that can be used to overcome performance limitations in JavaScript. Wasmage is a lightweight WebAssembly runtime for building cloud-native and edge-based applications. It provides a high-performance container for running React server-side functions on edge servers. WebAssembly has a smaller footprint and faster performance, making it ideal for Edge applications. It also provides isolation and protection for improved security.

♪ Hello, everyone. I'm Shivai Lamba. I'm Wasim Edge Ambassador and also a TensorFlow.js SIG and Working Group Lead from India. Welcome to my talk at React Advanced. I'm presenting virtually from India. The title of my talk is server-side rendering using Web7b, so let's get started.

The first thing we'll talk about is how do we actually achieve server-side rendering. Now, the traditional ways is either to, let's say, use a React framework like NestJs that actually supports server-side rendering out of the box, or, if you are one of those engineers who would want to set up a server-side rendering manually, you could create a fresh Redux store on every request that gets sent out and then get this data out of the store and perform the server-side rendering, or another alternative way is also to actually set up a Express server that can be used to serve the contents from the build directory as static files to your front end.

So, first, before we move on to how you can achieve server-side rendering with WebAssembly, let's talk about WebAssembly a bit more. So, WebAssembly is a language that is neither related to web directly or related to the assembly language itself. What it is is really an efficient, low-level bytecode that is highly performant and is portable, secure, and language-agnostic compilation-tacked. So that means you can basically take any of your highly performant programming languages like C++, or even scripting languages such as Python or Go, and compile it into a WebAssembly bytecode that can be directly used. Now, why has it been so popular is that it can basically reduce some of the disadvantages that we have in terms of performance, especially with JavaScript. And can overcome those performance limitations by using the more performant programming languages like C++ or Rust, and converting them into WebAssembly, and then running them on the browser alongside JavaScript. And now WebAssembly is not just limited to the frontend or the browser, and finds a lot of different use cases in server-side and cloud applications as well.

And what is Wasmage? So Wasmage is a lightweight WebAssembly runtime that is primarily focused on building a lot of cloud-native and edge-based applications, and Wasmage is currently a CNC, which is the Cloud Native Computing Foundation Sandbox project. So, the question is that, how can WebAssembly be used to actually implement the server-side rendering? So, Wasmage, as we mentioned, it's the runtime for WebAssembly, especially for edge devices. The Wasmage JavaScript SDK runtime actually provides a lightweight and high-performance container, which can run both JavaScript and also the React server-side functions on edge servers. So let's say if you have very limited resources and very less computation power, then you can run these lightweight WebAssembly containers on edge applications and still be able to have performance functions being run very smoothly. And the Wasmage Quick JS, which Quick JS is basically very similar to how V8 functions, so it's a JavaScript engine, and the Wasmage Quick JS engine is able to actually render React app-based components on the server-side and then basically send that rendered HTML as a string to the browser. And it primarily supports both the static-side rendering and also the streaming rendering that is provided from the server-side. But the biggest question is that why should we use WebAssembly in the first place to implement server-side rendering? Because we already have such popular frameworks such as Next.js and also you can set it up manually with Node.js. There are primarily two different reasons I'd like to point out why WebAssembly is useful. Now, compared to the standard approach in which the V8 runs, it uses Node.js and a Linux-based environment. Wasmage and especially WebAssembly has a much smaller footprint in terms of the overall size and how quickly you can actually spin up a WebAssembly-based container. So in terms of performance, it's a lot more faster and especially when you're working with very limited resources on an Edge application or an Edge device. And this does help with more improved load times and performance gains, especially if you're running your applications on the Edge. And secondly, the Wasmage also provides isolation and protection because of how WebAssembly manages memory by providing a sandbox layer around whatever application that you're using with WebAssembly. So that means that the Wasmage implementation for server-side rendering is able to basically execute whatever code is being run in that sandbox environment that is the footfall for how WebAssembly actually works. And that's one of the biggest benefits of performance and both in terms of privacy as well.

2. Enabling Server-Side Rendering with WebAssembly

Short description:

Learn how to enable server-side rendering with WebAssembly using a Create React app. Install Rust, Wasi, Wasm Edge, and the Quake.js Wasm Edge Toolkit. Convert your code into server-side rendering using the Wasm Edge container. Create a Node.js app to render the React.js code on the server. Build and deploy the application using rollup.js. Add dependent packages to package.json and update the script section to run the Wasmic server.

So let's take a very quick glimpse into how you can actually enable server-side rendering with WebAssembly with a very simple Create React app that if you have already used React, you might have used the Create React app.

So the first thing is to basically install some of the dependencies. So this includes installing a programming language, which is Rust because we'll be basically compiling the Rust code into a Wasm, that is a WebAssembly executable. Then we'll also use the Wasi, Wasi is the WebAssembly system interface that allows you to basically interact with the server-side and the even networking components of your computer. And then we'll also install the Wasm Edge, which is the runtime for WebAssembly, the CLI for that, and the Quake.js Wasm Edge Toolkit as well. So we have provided those links on the slides. You can go through and install these separately.

Once you have done that, we'll just go ahead and install a very simple React app using the nbx-create-react-app. And now we actually come to the most important step, which is actually converting our code into server-side rendering. So primarily what we're going to be doing is that we're going to be using the Wasm Edge container, which will be able to run our server-side rendering code and be able to actually run our React JavaScript. So first, let's create a new directory which will be server, and within that, we'll create a new file, index.js. Now you can basically populate that content of that index.js by going to this file that I've created, and you'll find that code over here. It's primarily just going ahead and running a simple Node.js app, and this also is able to... It also has some components related to the WebAssembly, where we are basically rendering the actual server, basically the code of the React.js code inside of our Node back end. So I'd recommend you to go and check out this particular code base, and once you have done that, once you have added this particular code to your index.js file, then we'll proceed. But this will answer what's happening behind the scenes.

So basically the server that we are creating right now, which is the Node server, that is basically rendering the app component, and instead of sending this app component to the front end, what we are doing is instead we are sending that rendered HTML back to the browser. And primarily if we see that in standard cases with React, the React DOM server rendered string is used to typically render the app to an HTML string. And basically that's what we are sending to our browser in this case. So you're basically now, what we are doing is that the app's content is being injected into the dev element with an ID of the router. And now it's being sent back as an HTTP response to the web browser.

Now once you have created that index.html file, index.js file, we'll go ahead and build and deploy our application with the help of rollup.js. Again, we have provided a config file for rollup in case you are interested to use that. Again, that is providing the second gist, which is over here, which is the rollup.config.js. This is responsible for not only going ahead and building, but also deploying the server-side code that we have created inside of the index.js file. So once we go ahead and deploy our code with the help of rollup.js, the last few things that are left is first of all adding some of the dependent packages into our package.json file. These are mostly related to the rollup package that we have just installed in our previous slide. And the last thing that we have to do is updating our script section. So this is primarily used to be able to actually run the Wasmic server from the Wasmic CLI that will help us to first take our REST code and convert it into the WebAssembly bytecode. And then actually this will serve the purpose of also taking your QuickJS code, which also invokes the webpack and the configuration file.

3. Server-Side Rendering and WebAssembly

Short description:

Learn how to build and render your application using server-side rendering and WebAssembly. See the changes in the app before and after enabling server-side rendering. Support for React 18 and the ability to create streaming applications using WebAssembly. Connect with me on Twitter at TheCloudWeb for more information on WebAssembly.

And this will be help to solve our build output and so that do our front-end. And finally we'll just go ahead and run the following commands to first go ahead and build our application and then render the HTML string on the browser.

And finally, before we see what exactly takes place or what's the output, so let's examine what is the actual change in the app before and after we have actually enabled the service and rendering with the help of WebAssembly.

So previously, the HTML source was simply just putting out the template with the server-side rendering placeholders. But now, once the server-side function is running on the server and we are fetching our HTML, the generated HTML stream from the server and we are rendering it onto a browser, you can see that in the lower corner, what you can see is that now we also get this data react route. Now, this is what is being fetched from our server that is rendering our static files, and that's what is being rendered now on the browser. And that's how you will basically start to see it in live action, once you start rendering it.

So, what's more in terms of support for server-side rendering with WebAssembly? There's a current support for React 18, which is the latest version of React, and you can also actually create streaming applications because of the functionality that comes with WebAssembly. It allows you to actually create streaming applications because of the way in how WebAssembly actually loads itself on the browser. Instead of, let's say a static JSON file, the WebAssembly bytecode basically comes under a streaming fashion and gets loaded into the browser in a streaming fashion. So you can also create streaming applications, the one that we showed was a static application. With that, I'd like to conclude my talk. Thank you so much. In case you're interested to know more, you can connect with me on my Twitter, at TheCloudWeb. I keep posting a lot on WebAssembly and WebAssembly is a really futuristic technology and one of the technologies to look out for, especially today and in the next few years. Especially for both applications on the front-end browser, and also equally on the server side and in cloud applications. With that in mind, thank you so much and I hope that you enjoy React Advanced.

Check out more articles and videos

We constantly think of articles and videos that might spark Git people interest / skill us up or help building a stellar career

React Advanced Conference 2022React Advanced Conference 2022
25 min
A Guide to React Rendering Behavior
React is a library for "rendering" UI from components, but many users find themselves confused about how React rendering actually works. What do terms like "rendering", "reconciliation", "Fibers", and "committing" actually mean? When do renders happen? How does Context affect rendering, and how do libraries like Redux cause updates? In this talk, we'll clear up the confusion and provide a solid foundation for understanding when, why, and how React renders. We'll look at: - What "rendering" actually is - How React queues renders and the standard rendering behavior - How keys and component types are used in rendering - Techniques for optimizing render performance - How context usage affects rendering behavior| - How external libraries tie into React rendering
React Summit Remote Edition 2021React Summit Remote Edition 2021
33 min
Building Better Websites with Remix
Remix is a new web framework from the creators of React Router that helps you build better, faster websites through a solid understanding of web fundamentals. Remix takes care of the heavy lifting like server rendering, code splitting, prefetching, and navigation and leaves you with the fun part: building something awesome!
React Advanced Conference 2022React Advanced Conference 2022
30 min
Using useEffect Effectively
Can useEffect affect your codebase negatively? From fetching data to fighting with imperative APIs, side effects are one of the biggest sources of frustration in web app development. And let’s be honest, putting everything in useEffect hooks doesn’t help much. In this talk, we'll demystify the useEffect hook and get a better understanding of when (and when not) to use it, as well as discover how declarative effects can make effect management more maintainable in even the most complex React apps.
React Summit 2023React Summit 2023
32 min
Speeding Up Your React App With Less JavaScript
Too much JavaScript is getting you down? New frameworks promising no JavaScript look interesting, but you have an existing React application to maintain. What if Qwik React is your answer for faster applications startup and better user experience? Qwik React allows you to easily turn your React application into a collection of islands, which can be SSRed and delayed hydrated, and in some instances, hydration skipped altogether. And all of this in an incremental way without a rewrite.
React Summit 2022React Summit 2022
20 min
Routing in React 18 and Beyond
Concurrent React and Server Components are changing the way we think about routing, rendering, and fetching in web applications. Next.js recently shared part of its vision to help developers adopt these new React features and take advantage of the benefits they unlock.In this talk, we’ll explore the past, present and future of routing in front-end applications and discuss how new features in React and Next.js can help us architect more performant and feature-rich applications.

Workshops on related topic

React Summit 2023React Summit 2023
170 min
React Performance Debugging Masterclass
Featured WorkshopFree
Ivan’s first attempts at performance debugging were chaotic. He would see a slow interaction, try a random optimization, see that it didn't help, and keep trying other optimizations until he found the right one (or gave up).
Back then, Ivan didn’t know how to use performance devtools well. He would do a recording in Chrome DevTools or React Profiler, poke around it, try clicking random things, and then close it in frustration a few minutes later. Now, Ivan knows exactly where and what to look for. And in this workshop, Ivan will teach you that too.
Here’s how this is going to work. We’ll take a slow app → debug it (using tools like Chrome DevTools, React Profiler, and why-did-you-render) → pinpoint the bottleneck → and then repeat, several times more. We won’t talk about the solutions (in 90% of the cases, it’s just the ol’ regular useMemo() or memo()). But we’ll talk about everything that comes before – and learn how to analyze any React performance problem, step by step.
(Note: This workshop is best suited for engineers who are already familiar with how useMemo() and memo() work – but want to get better at using the performance tools around React. Also, we’ll be covering interaction performance, not load speed, so you won’t hear a word about Lighthouse 🤐)
React Advanced Conference 2021React Advanced Conference 2021
132 min
Concurrent Rendering Adventures in React 18
Featured WorkshopFree
With the release of React 18 we finally get the long awaited concurrent rendering. But how is that going to affect your application? What are the benefits of concurrent rendering in React? What do you need to do to switch to concurrent rendering when you upgrade to React 18? And what if you don’t want or can’t use concurrent rendering yet?

There are some behavior changes you need to be aware of! In this workshop we will cover all of those subjects and more.

Join me with your laptop in this interactive workshop. You will see how easy it is to switch to concurrent rendering in your React application. You will learn all about concurrent rendering, SuspenseList, the startTransition API and more.
React Summit Remote Edition 2021React Summit Remote Edition 2021
177 min
React Hooks Tips Only the Pros Know
Featured Workshop
The addition of the hooks API to React was quite a major change. Before hooks most components had to be class based. Now, with hooks, these are often much simpler functional components. Hooks can be really simple to use. Almost deceptively simple. Because there are still plenty of ways you can mess up with hooks. And it often turns out there are many ways where you can improve your components a better understanding of how each React hook can be used.You will learn all about the pros and cons of the various hooks. You will learn when to use useState() versus useReducer(). We will look at using useContext() efficiently. You will see when to use useLayoutEffect() and when useEffect() is better.
React Advanced Conference 2021React Advanced Conference 2021
174 min
React, TypeScript, and TDD
Featured WorkshopFree
ReactJS is wildly popular and thus wildly supported. TypeScript is increasingly popular, and thus increasingly supported.

The two together? Not as much. Given that they both change quickly, it's hard to find accurate learning materials.

React+TypeScript, with JetBrains IDEs? That three-part combination is the topic of this series. We'll show a little about a lot. Meaning, the key steps to getting productive, in the IDE, for React projects using TypeScript. Along the way we'll show test-driven development and emphasize tips-and-tricks in the IDE.
React Advanced Conference 2021React Advanced Conference 2021
145 min
Web3 Workshop - Building Your First Dapp
Featured WorkshopFree
In this workshop, you'll learn how to build your first full stack dapp on the Ethereum blockchain, reading and writing data to the network, and connecting a front end application to the contract you've deployed. By the end of the workshop, you'll understand how to set up a full stack development environment, run a local node, and interact with any smart contract using React, HardHat, and Ethers.js.
React Summit 2023React Summit 2023
151 min
Designing Effective Tests With React Testing Library
Featured Workshop
React Testing Library is a great framework for React component tests because there are a lot of questions it answers for you, so you don’t need to worry about those questions. But that doesn’t mean testing is easy. There are still a lot of questions you have to figure out for yourself: How many component tests should you write vs end-to-end tests or lower-level unit tests? How can you test a certain line of code that is tricky to test? And what in the world are you supposed to do about that persistent act() warning?
In this three-hour workshop we’ll introduce React Testing Library along with a mental model for how to think about designing your component tests. This mental model will help you see how to test each bit of logic, whether or not to mock dependencies, and will help improve the design of your components. You’ll walk away with the tools, techniques, and principles you need to implement low-cost, high-value component tests.
Table of contents- The different kinds of React application tests, and where component tests fit in- A mental model for thinking about the inputs and outputs of the components you test- Options for selecting DOM elements to verify and interact with them- The value of mocks and why they shouldn’t be avoided- The challenges with asynchrony in RTL tests and how to handle them
Prerequisites- Familiarity with building applications with React- Basic experience writing automated tests with Jest or another unit testing framework- You do not need any experience with React Testing Library- Machine setup: Node LTS, Yarn