Delve into building a GraphQL endpoint with Deno, compare technologies, configure queries, and integrate PostgresSQL and MongoDB databases to create a secure, high-performing application.

deno.tar.gz

Deno version

Deno run

deno_run_application

deno_run_db

deno_run_application_server_ts_file

docker-deno

Deno is a modern and secure runtime for JavaScript. It was created by the same team that created Node.js. Deno offers better performance, security, and simplicity than any other JavaScript runtime.

In this course, you will start by understanding the different technologies used in Deno, such as Typescript. You will compare these technologies with JavaScript and GraphQL as well as learn their terminologies. Then, you will create your own endpoint with Deno and configure queries and mutations in it. Next, you will explore two different databases with Deno: first, you’ll learn how to set up an SQL database using PostgresSQL and then how to configure a NoSQL database using MongoDB to store documents and collections of on-demand data. Finally, you’ll put everything together to have a fully functioning GraphQL endpoint made with Deno and backed by PostgreSQL and MongoDB. 

After this course, you’ll be able to create a Deno application and a GraphQL endpoint while having a database of your choice to store data.

Building a GraphQL Endpoint with Deno

## Overview

Docker was initially launched in 2011 and was quickly adopted by a large number of developers. You can think of Docker as a virtualization software platform that runs containers. A container is a light version of a VM. Before Docker, when working with different projects (such as a microservice), we had two options: put all the different applications on the same server, or create a VM for each one.

The first approach means that when an application fails and breaks something in the OS configuration, all the other applications also fail, which is terrible when trying to develop a very important application.

The second approach means that we would need too many resources to run different VMs, which poses other issues (like the high cost of resources).

# Overview

Docker was initially launched in 2011 and was quickly adopted by a large number of developers. You can think of Docker as a virtualization software platform that runs containers. A container is a light version of a VM. Before Docker, when working with different projects (such as a microservice), we had two options: put all the different applications on the same server, or create a VM for each one.

The first approach means that when an application fails and breaks something in the OS configuration, all the other applications also fail, which is terrible when trying to develop a very important application.

The second approach means that we would need too many resources to run different VMs, which poses other issues (like the high cost of resources).

Introduction to Deno, TypeScript, and GraphQL

Creating a Basic GraphQL Endpoint

Databases and Deno

SQL: Postgres and Deno

NoSQL: Mongo and Deno

Wrapping Up

Appendix

Introduction to Docker

Overview