For the upcoming sprint, our focus is on implementing the server side of our application. To proceed effectively, we require a robust database schema. We will base our schema design on the guidelines outlined in our Software Design Document, feel free to update the existing schema.
Additionally, we need to make a decision regarding the database service we'll utilize. We have two options:
Create our own REST API: Following industry best practices outlined in resources like this guide, we will develop a custom REST API tailored to our application's needs with postgreSQL as our database.
Utilize Firebase: Leveraging the capabilities of Firebase Firestore, we can rapidly integrate a scalable NoSQL database into our project.
We also need primary people to take on these roles.
For the upcoming sprint, our focus is on implementing the server side of our application. To proceed effectively, we require a robust database schema. We will base our schema design on the guidelines outlined in our Software Design Document, feel free to update the existing schema.
Additionally, we need to make a decision regarding the database service we'll utilize. We have two options:
Create our own REST API: Following industry best practices outlined in resources like this guide, we will develop a custom REST API tailored to our application's needs with postgreSQL as our database.
Utilize Firebase: Leveraging the capabilities of Firebase Firestore, we can rapidly integrate a scalable NoSQL database into our project.
We also need primary people to take on these roles.