Skip to content
This repository has been archived by the owner on May 10, 2024. It is now read-only.

ADR 10 (MongoDB)

RubenFern edited this page Mar 14, 2024 · 1 revision

ADR 10 (MongoDB)

Decision

We decided to use MongoDB because we needed a database that would provide us with speed as opposed to the consistency offered by other databases for storing and querying questions. In addition, because it works by indexing documents, we have Atlas Search which optimizes the search for documents.

Status

Accepted.

Consequences

A second database had to be added to the game service, bringing us closer to a real microservices architecture.

Risks

The scalability of MongoDB, it is possible that the service performs too many queries to the database and although MongoDB has a horizontal scalability, increasing the number of nodes can cause bottlenecks and affect the display of queries during the game.