Repository navigation
Database
Keegan edited this page May 17, 2026
·
18 revisions
We separate the user database from the database that the services have access to. All information from the separated users database is passed to functions that in it using the JWT. We have two databases.
The users database is used for authentication upon log in and responsible for the authorization for the requests since it helps to bind the user's role to the JWT.
Users
| Column | Type | Description |
|---|---|---|
| UserId | UUID | |
| UserEmail | VARCHAR(255) | |
| UserName | VARCHAR(100) | |
| UserRole | User_Role_Enum | |
| UserPassword | VARCHAR(255) | |
| UserJWTIssued | TIMESTAMPTZ |
- User Stories
- Use Cases
- Use Case Diagrams
- Functional Requirements
- API Service Contracts
- Quality Requirements
- Constraints
- Technologies Required
- Architecture Diagram
- Domain Model
- Introduction
- User Stories
- Use Case Diagrams
- Functional Requirements
- Non-Functional Requirements
- Domain Model
- Introduction
- User Stories
- Use Case Diagrams
- Functional Requirements
- Non-Functional Requirements
- Domain Model
- Introduction
- Architectural Requirements
- Technology Requirements
- API Contracts
- Deployment
- NFR Testing
- NFR Traceability Matrix
- Introduction
- User Stories
- Use Case Diagrams
- Functional Requirements
- Non-Functional Requirements
- Domain Model
- Introduction
- Architectural Requirements
- Technology Requirements
- API Contracts
- Deployment
- NFR Testing
- NFR Traceability Matrix