Book Image

A Blueprint for Production-Ready Web Applications

By : Dr. Philip Jones
Book Image

A Blueprint for Production-Ready Web Applications

By: Dr. Philip Jones

Overview of this book

A Blueprint for Production-Ready Web Applications will help you expand upon your coding knowledge and teach you how to create a complete web application. Unlike other guides that focus solely on a singular technology or process, this book shows you how to combine different technologies and processes as needed to meet industry standards. You’ll begin by learning how to set up your development environment, and use Quart and React to create the backend and frontend, respectively. This book then helps you get to grips with managing and validating accounts, structuring relational tables, and creating forms to manage data. As you progress through the chapters, you’ll gain a comprehensive understanding of web application development by creating a to-do app, which can be used as a base for your future projects. Finally, you’ll find out how to deploy and monitor your application, along with discovering advanced concepts such as managing database migrations and adding multifactor authentication. By the end of this web development book, you’ll be able to apply the lessons and industry best practices that you’ve learned to both your personal and work projects, allowing you to further develop your coding portfolio.
Table of Contents (13 chapters)
Part 1 Setting Up Our System
Part 2 Building a To-Do App
Part 3 Releasing a Production-Ready App

Updating packages

A very common source of vulnerabilities in web applications is vulnerable dependent packages. This is especially true if the application is using an older version of a package when a new, more secure version is available. To mitigate against this, we can periodically check for known vulnerabilities and, crucially, update the packages as often as possible.

Importance of lockfiles

By using npm and PDM, we are using lockfiles; this means that we’ll always install the same package version on any system until we change the lockfile. Without a lockfile, we would quickly be in a position where different systems run with different package versions and potentially different packages. This would make it hard to diagnose bugs, as it may depend on a version we aren’t testing. Crucially though, it would make our app less secure as we would have no control over what was installed.

Periodically checking for vulnerabilities

In our app, we are using many...