Server-side rendering

As explained in Rust Servers, Services, and Apps

Server-side rendering is a web application pattern in which a server generates a fully rendered web page and sends it to a browser.

Server-side rendering (SSR) generates a complete web page on the server and sends it to the browser. The server combines a template with data to create pages containing static and dynamic content. section 7.1

In a Rust web app, Actix Web handlers can use Tera templates to build dynamic pages for HTTP responses. Forms submit input to routes; handlers process it and return pages, while template control flow can display data-backed lists. section 7.8

Static and dynamic pages

A bank homepage can be the same for every visitor, while an account page shows a customer’s balances and statements. An EzyTutors storefront could render tutor course lists and details. section 7.1 section 1.3.1

Figure 7.1 Server-side rendering of web pages

Follow the components involved in rendering a server-generated page. section 7.1

How Rust Servers, Services, and Apps covers it

How deep it goes

Traces templates, handlers, forms, and rendered responses; leaves SPA development for later and excludes PWAs.

Examples

Uses bank home and account pages, plus tutor course listings and details, to illustrate static and dynamic content.

What you can do after

Apply Actix Web and Tera to render dynamic pages, process form submissions, and display data-backed lists.

How it connects

Connects SSR to template engines, Actix Web, Tera, HTML forms, and backend web services.

liveBookmanning.com

Read Rust Servers, Services, and Apps on liveBook Get the book at manning.com

Also explained in

• 

  liveBookmanning.com
  Modern AngularServer-side rendering is the generation of an application's initial HTML on a server before it is delivered to the browser.
• 

  liveBookmanning.com
  React in DepthServer-side rendering is the process of producing application interface output on a server before sending it to the client.
• 

  liveBookmanning.com
  ASP.NET Core in Action, 3eServer-side rendering is the process of generating HTML on the server before sending it to a client.
• 

  liveBookmanning.com
  React Quickly, Second EditionServer-side rendering is the generation of user-interface markup on a server before it is delivered to a client.
• 

  liveBookmanning.com
  Build a Frontend Web Framework (From Scratch)A rendering approach in which the server generates the HTML for an application before sending it to the browser.
• 

  liveBookmanning.com
  Pro Angular 16Server-side rendering is the technique of executing an application on a server to generate HTML that is sent to a browser before client-side code is ready.
• 

  liveBookmanning.com
  Django in ActionServer-side rendering is the composition of a web page's HTML on the server before it is sent to a browser.

Compare how 8 books explain server-side rendering →

Related concepts

• prerenderingalternative to · Prerendering is the generation of web-page HTML before it is requested or served, typically as prebuilt files.
• single-page applicationcontrasts with · A single-page application is a web application that loads a document and dynamically updates its content or interface without full-page navigation for most interactions.
• HTMLproduces · HTML (HyperText Markup Language) is the standard markup language for structuring content and elements in web documents.
• client-side renderingcontrasts with · Client-side rendering is the generation or updating of a web interface in a user's browser by code executed there.
• template engineuses · A template engine is software that combines reusable templates with data and rules to generate rendered output such as text, documents, or user-interface views.

This explainer was generated by Manning's knowledge graph from the text of Rust Servers, Services, and Apps. The section links point to the parts of the book it draws on.