feat(design) added technologies table

This commit is contained in:
ribardej
2025-09-18 13:29:11 +02:00
parent 71b9fa7b5f
commit 0c91561f19

View File

@@ -57,11 +57,11 @@ flowchart LR
- Core entities and relationships (ER sketch or brief description).
- Example records or schemas (link to files or include concise snippets).
- Users, Transactions, Transaction_Categories, User_settings
### 2.3 APIs (REST/gRPC/GraphQL)
- Interface style and rationale.
- Link to OpenAPI/Proto files, or list a few key endpoints/RPCs.
- Swagger
## 3. Technologies
@@ -69,7 +69,15 @@ List the cloud services, libraries, and tools you will use and why.
| Technology / Service | Role / Where Used | Why chosen (brief) | Alternatives considered |
| -------------------- | ----------------- | ------------------ | ----------------------- |
| | | | |
| Python | Back-End | Simplest for both of us | Java, C#, PHP |
| React | Front-End | Most popular, we dont have exp with FE | Vue, plain JS |
| REST | BE<->FE API | Simplest | GraphQL |
| MariaDB | Database | Prior experience | PostgreSQL, CockroachDB |
| Redis | Cache | Prior experience | Valkey, Memcached |
| RabbitMQ | Message queue | Prior experience | MQTT, Redis |
| Python Fast API | API Framework | Simplicity | Flask, Django |
| Open Tofu | Cluster deployment | Prior experience | Terraform |
| Talos Cluster | Deployment | Why not | Docker swarn, RKE |
Notes: