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

Our application went through a big change in this chapter!

We started by migrating our application from the standard library HTTP module to Oak. Not only did we migrate the logic to serve the app, but we also started to define some routes using Oak's router. We noticed that the application logic started to become simpler as Oak encapsulated part of the job that was done manually previously. We managed to migrate all the HTTP code from the standard library without having to change the business logic, which is a very good sign that we're doing well in terms of application architecture.

We kept moving and learned how to listen and handle events in an Oak application. As we started writing more code, we also became more familiar with Oak, understanding its functionalities, exploring its documentation, and experimenting with it.

Users are an important part of any application and with that in mind, we also spent a big part of this chapter focusing on them. We...