Schema of the Database + Endpoints

[ArfatSalman]

Instructions

Since you have built the frontend, and you have used fake data till now, now is the time to decide what data your database will store and what the shape of the data is going be.

For this issue, you have to decide on which type DB to use (for ex - SQL / Mongo / Neo4J etc) and what tables (or collections) you app is going to have. Apart from that, also describe the fields of the tables and their types. Ensure to list down constraints such as Foreign Key. In short, you have

Since the back-end is an REST-based service, what URLs will your backend expose? Try to write all the end points and how many HTTP verbs they support.

Requirements

• Make a Git tag called "frontend-1.0" in your frontend repo.
• Decide on a DB service (Heroku SQL service / Mongo mLab) and provision a DB of your choice by making a few sample tables / collections.
• Describe the DB schema with validation checks, constraints etc.
• Seed your DB with the fake data already present in your front-end.
• Implement the user sign-up / login (if you haven't already) in the backend.
  • Integrate this backend feature with the frontend.
• Give descriptions of the endpoints that the backend will eventually have. (see above). You should at least tell the endpoint, the purpose, accepted HTTP verbs, possible HTTP response codes.

Resources

Please ensure that you read these articles well.

• Best Practices for API design
• API design Architecture
• What are DB Schemas
• Tutorial on DB Schema Design
• DB Design - Bad Practices
• DB Design - Best Practices
• DB Diagram