doc: added backend architecture diagram #107
No reviewers
Labels
No labels
CI/CD
MongoDB
PostgreSQL
api
authentication
bug
documentation
duplicate
enhancement
example issue
fix
good first issue
help wanted
high-level requirement
infrastructure
invalid
low-level requirement
medium-level requirement
question
security
test
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AndreFerreira5/starranja!107
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/arch-diagram"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
simply adding an architecture diagram to the docs folder so the developers get a better understanding of how the backend is supposed to work and how it is structured.
(closes #106)
great diagram, shows everything we need to understand the backend flow
The architecture diagram looks clear and correctly distinguishes all the modules as well as detailing all interactions and relations. It is easy to understand and gives readers a good overview of the architecture.