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.
Server-Side Rendering Using WebAssembly
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
♪ 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.
2. Enabling Server-Side Rendering with WebAssembly
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.
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
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.