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

Exploring Deno HTTP frameworks

When you're building an application that's more complex than a simple tutorial, and if you don't want to take a purist approach, you are most likely going to use third-party software.

Obviously, this is not something particular to Deno. Even though there are communities that are keener on using third-party modules than others, all the communities use third-party software.

We could go over the reasons why people do or don't do this, but the more popular reasons are always to do with reliability and time management. This might be because you want to use software that is battle tested instead of building it yourself. Sometimes, it is a mere time management question of not wanting to rewrite something that has already been created.

One important thing we have to say is that we must be extremely cautious in terms of how many of the applications we're building are coupled with third-party software. We don't mean that...