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

# What we learned

We used two databases in this course:

* We used Postgres as a SQL database, which is one of the most commonly-used databases out there. It has very good documentation, and it’s always recommended for new users of SQL databases to utilize it. Once you’ve gained some proficiency, you can switch to another database if you need to.

* We then used MongoDB, which is one of the most commonly-used NoSQL databases. Working with NoSQL databases is a bit different since you have different types of databases (document, graph, key-value) that are adapted for a particular usage.


## HTTP endpoints

In the course, we didn’t go with the classic REST APIs. Instead, we used GraphQL. Each option has it’s pros and cons, which we discussed earlier in this course.

Before using GraphQL for your projects, you should always check the potential impact it could have on your existing ecosystem to see if it’s a good choice.

Using REST is easy with Deno. At its core, it doesn’t differ too much from the GraphQL approach, since you can still keep all the services and your data access models.

Let’s wrap up this course with a recap of what we did and a few final words.

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

Conclusion

What we learned

HTTP endpoints