📁 Project Structure (Monorepo, Dockerized Microservices)

/match-made/
├── services/
│   ├── user-service/
│   ├── game-service/
│   ├── auth-service/
│   ├── matchmaking-service/
│   ├── feedback-service/
│   ├── notification-service/
│   └── analytics-service/
├── common/                 # Shared libs (e.g., JWT, event schemas)
├── deploy/
│   ├── docker-compose.yml
│   └── k8s/ (future)
├── scripts/                # Local dev bootstrap, seeders, tests
├── docs/                   # OpenAPI specs, architecture diagrams
├── Makefile                # Dev commands
└── .github/workflows/      # CI/CD

🧰 Stack Choices Summary (Locked In)

✅ Framework Workstreams

1. Code Structure per Service

Each service has:

• /app folder with:
  • main.py
  • api/routes.py
  • models.py
  • core/config.py
  • events/publisher.py
• Dockerfile
• requirements.txt

2. Shared Libs (/common)

• jwt_utils.py
• event_bus.py
• schemas/ (Pydantic event contracts)
• Reusable error/response models

3. Dev Environment