Planning

We will go through the thought process of planning an application.

Before going any further, it's important that we take time to plan the project, to get an understanding of what will be needed. This should always be the first step when creating an application: deciding the scope and potentially required features. I like to do this with the following three steps, but everyone works differently, so find the way which is best for you:

  1. Decide on features

  2. Create a database diagram

  3. Plan endpoints

Sometimes I switch 2 and 3 depending on the project, which will be the case for this project.

By planning out your project like this, you'll save a lot of time down the line when you come to develop the application, as you will have a blueprint to follow.

The grand plan#

We will continue our idea from the last module for a bare bones Twitter clone which we will call Quacker 🦆.

Features#

The application will consist of a Quack (tweet) board which will list recent Quacks in descending order (most recent first). It will also allow for a new Quack submission from any logged in Ducks (users), and of course allow for a Duck to register and log in. You should also allow for each Quack to receive aCrumb (like), so we need to keep track of which Duck has given Crumbs to which Quacks. Lastly we also want a health-check (status) endpoint to check if our application is running.

Endpoints#

From the information above, we can deduce that our application will need the following endpoints:

 

This page is a preview of Build and deploy a REST API with Deno

Start a new discussion. All notification go to the author.