Book Image

Deno Web Development

By : Alexandre Portela dos Santos
Book Image

Deno Web Development

By: Alexandre Portela dos Santos

Overview of this book

Deno is a JavaScript and TypeScript runtime with secure defaults and a great developer experience. With Deno Web Development, you'll learn all about Deno's primitives, its principles, and how you can use them to build real-world applications. The book is divided into three main sections: an introduction to Deno, building an API from scratch, and testing and deploying a Deno application. The book starts by getting you up to speed with Deno's runtime and the reason why it was developed. You'll explore some of the concepts introduced by Node, why many of them transitioned into Deno, and why new features were introduced. After understanding Deno and why it was created, you will start to experiment with Deno, exploring the toolchain and writing simple scripts and CLI applications. As you progress to the second section, you will create a simple web application and then add more features to it. This application will evolve from a simple 'hello world' API to a web application connected to the database, with users, authentication, and a JavaScript client. In the third section, the book will take you through topics such as dependency management, configuration and testing, finishing with an application deployed in a cloud environment. By the end of this web development book, you will become comfortable with using Deno to create, maintain, and deploy secure and reliable web applications.
Table of Contents (15 chapters)
1
Section 1: Getting Familiar with Deno
5
Section 2: Building an Application
10
Section 3: Testing and Deploying

Summary

This was a chapter in which we focused a lot on practices that bring our application closer to a state that we can deploy into production. We started by exploring basic security practices, adding the CORS mechanism and HTTPS to the API. These two features, which are pretty much standard in any application, are a big security improvement on what we already had.

Also, thinking about deploying the application, we also abstracted the configuration and secrets from the code base. We started by creating an abstraction that would deal with it so that the configuration is not scattered, and modules just receive their configuration values without any awareness of how they're loaded. Then, we proceeded to using those values in our current code base, something that revealed itself to be quite easy. This step removed any configuration values from the code and moved them to a configuration file.

Once done with configuration, we used the same abstraction created to deal with secrets...