Research database choices
License and Copyright Notice
By submitting this issue or commenting on this issue, or contributing any content to this issue, you certify under the Developer Certificate of Origin that the content you post may be licensed under GPLv3 (for code) or CC-BY-SA 4.0 International (for non-code content).
What is the goal or the problem, and why is it important?
Research needs to be done before choosing a database to use for the service. It should be something fairly lightweight, expandable, and quick to learn.
/epic &6 (closed)
How are you going to achieve the goal or solve the problem?
Collect relevant information to the differences between the NoSql and MySql databases. If possible make a selection and an argument for that choice.
What will be produced as a result of this effort and where will it live on GitLab?
A list of URLs to the resources found in a comment. As well as information about the given database if time permits.
Give justification for weight or due date.
Collecting resources and making a decision shouldn't take to long, but there will be back and forth conversations regarding the decisions. These issues shouldn't take more than 2 - 3 days.
Who will do it, and what will they do?
@gcolon021 Was assigned to this issue.
What was the outcome?
After conducting a bit of research, MongoDB was chosen as the database for the project. This is due to the fact that it uses a JSON format for data and queries, which is what the project's chosen backend language JavaScript uses to represent objects. This will make it easy to translate between the JavaScript backend and the data.
Template Version 1.0.0
/label type::spike