Book Image

JavaScript Design Patterns

By : Hugo Di Francesco
Book Image

JavaScript Design Patterns

By: Hugo Di Francesco

Overview of this book

Unlock the potential of JavaScript design patterns, the foundation for development teams seeking structured and reusable solutions to common software development challenges in this guide to improving code maintainability, scalability, and performance. Discover how these patterns equip businesses with cleaner and more maintainable code, promote team collaboration, reduce errors, and save time and costs. This book provides a comprehensive view of design patterns in modern (ES6+) JavaScript with real-world examples of their deployment in professional settings. You’ll start by learning how to use creational, structural, and behavioral design patterns in idiomatic JavaScript, and then shift focus to the architecture and UI patterns. Here, you’ll learn how to apply patterns for libraries such as React and extend them further to general web frontend and micro frontend approaches. The last section of the book introduces and illustrates sets of performance and security patterns, including messaging and events, asset and JavaScript loading strategies, and asynchronous programming performance patterns. Throughout the book, examples featuring React and Next.js, in addition to JavaScript and Web API examples, will help you choose and implement proven design patterns across diverse web ecosystems, transforming the way you approach development.
Table of Contents (16 chapters)
1
Part 1:Design Patterns
5
Part 2:Architecture and UI Patterns
9
Part 3:Performance and Security Patterns

Client and server rendering with React

In a web context, client-side rendering is the process by which JavaScript is used inside a user’s browser to generate or update the page contents. A fully client-side-rendered application will only display meaningful content when the relevant JavaScript code has completed downloading, parsing, and running.

In the following sequence diagram, we use the term “origin” instead of something such as “server,” since one benefit of full client-side rendering is that the resources “serving” our content can be what’s called static hosting. This includes services such as AWS Simple Storage Service (S3), Netlify, Cloudflare Pages, and GitHub Pages, among others. There’s no dynamic server-side component in these services.

Figure 5.1: A client-side-rendering sequence diagram

Figure 5.1: A client-side-rendering sequence diagram

In contrast, server-side rendering denotes the process by which a server generates a full...