Skip to content

Architecture Decision 3

david alvarez edited this page May 1, 2024 · 2 revisions

Database Platform

Date

08/02/2024

Status

✅ Accepted

Context

We needed a database solution for our project to store user data and question data. The database needed to be scalable, flexible, and capable of handling a large amount of data.

Decision

We decided to use MongoDB as our database solution. MongoDB is a popular NoSQL database known for its scalability and flexibility. It allows us to store data in a flexible, JSON-like format which can be changed over time as our needs evolve.

Consequences

Choosing MongoDB means that we need to learn how to use this technology. This includes understanding its document-oriented model, learning how to create queries, and managing MongoDB deployments. However, we believe that the benefits of MongoDB outweigh the learning curve.

Alternatives

We considered other database solutions such as MySQL and Neo4j. MySQL is a popular relational database, but it requires a fixed schema which can be less flexible for our needs. Neo4j is a graph database which is great for handling complex relationships between data, but it might be overkill for our project's requirements.

Clone this wiki locally