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)
Section 1: Getting Familiar with Deno
Section 2: Building an Application
Section 3: Testing and Deploying


In this chapter, we finally started building an application that leverages our knowledge of Deno. We started by considering the main goals we will have when we build an application and define its architecture. These goals will set the tone for most of our conversations regarding architecture and structure throughout this book as we'll keep going back to them, ensuring that we're in line with them.

We started by creating our folder structure and trying to achieve our very first application goal: have an HTTP endpoint that lists museums. We did this by building the simple business logic first and progressed while needs such as separation of concerns and isolation and responsibilities arose. These needs derived our architecture, proving why the layers and abstractions we created are useful and demonstrating what they add.

By having the responsibilities and the module's interfaces well-defined, we understood that we could temporarily build our application by...