Fluent Web Development

Chapter 3. Networking

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 4th 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].

The Chapter 2 showed that structure and architecture in our applications are largely about communication between individual parts. This is common in software engineering and software architecture. However, web applications add another layer of complexity. Web applications must bridge the gap between client and server. They connect the user’s device with the computer of those providing the service, relying on one thing: a stable network.

In reality, the network is anything but stable. Especially on mobile devices, where users are constantly on the move, outages can occur more frequently. The interactive application on the client side often has no choice but to wait until a request finally completes and reports whether the transfer of the desired data was even successful. Impatient users will have already tried multiple times to press the reload button to finally get a result. In vain.

Different applications have different network requirements. Constant updates from the ...