Fluent Web Development

Chapter 4. Rendering

A Note for Early Release Readers

With Early Release ebooks, you get books in their earliest form—the author’s raw and unedited content as they write—so you can take advantage of these technologies long before the official release of these titles.

This will be the 5th chapter of the final book. Please note that the GitHub repo will be made active later on.

If you’d like to be actively involved in reviewing and commenting on this draft, please reach out to the editor at [e-mail].

In Chapter 3, we explored how HTTP shapes communication between client and server. We learned about request-response cycles, streaming, and the fundamental unreliability of the network. Now that we know how we communicate, we can focus on sending the right data to the right place to show users something presentable.

Whenever users view a website, they see the rendered version of the HTML we prepare. In frontend jargon, rendering also refers to the process of generating the HTML we ultimately want to display. To create this HTML, we have several options that can happen on either end of the network communication: client or server.

The exciting part is that none of these techniques are mutually exclusive. You can start on one side and continue on the other. Depending on the use case, a good mix might even be the perfect solution.

In this chapter, we’ll explore the possibilities of rendering. We’ll explore the three fundamental rendering models, examine the patterns modern ...