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 chapter pretty much wraps up our application in terms of logic. We'll come back later in Chapter 8, Testing – Unit and Integration, to add tests and the single feature that we're missing – the ability to rate museums. However, most of this has already been done. In its current state, we have an application that has its domains divided into modules that can be used by themselves and don't depend on each other. We believe we achieved something that is both easy to navigate in the code and extendable.

This concludes the process of constantly reworking and refining the architecture, managing dependencies, and tweaking logic to make sure code is as decoupled as possible, and as easy to change in the future as possible. While doing all of this, we managed to create an application with a couple of features, trying to go around industry standards at the same time.

We started this chapter by learning about middleware functions, something we&apos...