Build your fully functional RESTful server within 20 minutes!

based on NestJS and DynamoDB

With sads.js, you could provide powerful RESTful APIs in 20 minutes.

With sads.js, you don't have to start your projects with well-designed E-R diagrams and database designs. You don't have to log into the database manager and update database schemas and you don't have to run database migrations. You could easily change the database schemas because there are no physical schemas at all.

In summary, you could spend as less as possible on back-end and put more efforts on front-end design so that clients can see the scooter, the bicycle as early as possible.

How less do you have to work on back-end in the early stages (before motorbike) of the project?

• 20 minutes to start;
• 5-10 minutes for every new change;
• 2-3 days IN TOTAL

In principle, sads.js is applicable to the scenarios of

• Small scale data storage (no more than thousands) & medium level of complexity of entity relationships
• Large scale data storage with very simple entity relationships
• The data in the past are not allowed (or unnecessary) to be changed

Therefore, sads.js is pretty good at building scrum projects which started normally with only a couple of concepts without any detailed requirements, just like:

• Projects for PoC (Proof of Concept)
• Personal projects (normally with very small data storage)

$ npm install

please refer to dynamodb/README.md

# development
$ npm run start

# watch mode
$ npm run start:dev

# production mode
$ npm run start:prod

then launch your browser and navigate to the Swagger UI: http://localhost:3000/api

# unit tests
$ npm run test

# e2e tests
$ npm run test:e2e

# test coverage
$ npm run test:cov

• is used as id (just like in RDBMS),
• should be a string BUT NOT AN INTEGER;
• contains a guid/uuid string;

• is used as the entity name;
• should be a string in the format of "appName(optional) + entityName"

Consider the relationship below

With the N side entity as the base entity, here are the sample sads.js entities

Department

Employees

Consider the relationship below

• Set Order as the base entity. Then you don't have to do anything with Order
• Set Item.sk as OrderId. Saying, Item.sk = Order.pk

Here are the sample records:

Orders

Items

• Author - Derek Ji