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

Connecting to MongoDB

So far, we've implemented an application that lists museums, and contains users, allowing them to authenticate. These features are already in place, but they all have a catch: they're all running against an in-memory database.

We've decided to do it this way for the sake of simplicity. However, since most of our implementation doesn't depend on the delivery mechanism, it shouldn't change much if the database changes.

As you might have guessed by this section's title, we'll learn how to move one of the application entities to the database. We'll leverage the abstractions we've created in order to do this. The process will be very similar to all the entities, and thus we've decided on learning how to connect to a database just for the users' module.

Later, if you are curious about how this would work if all the applications were connected to the database, you'll have the opportunity to check...