MVC Hexagonal Clean

Component-internal architecture patterns: Model-View-Controller, Ports & Adapters (Hexagonal), Clean Architecture — separating business logic from infrastructure.

Why we need this / what value this brings

Separating business logic from infrastructure (DB, HTTP, external APIs) makes the core logic testable without spinning up real infrastructure.

When to use this

Worth adopting once business logic is complex enough that testing it requires excessive mocking of infra, or infra needs to be swappable.

How to use or implement this

Define the domain logic against interfaces/ports; implement adapters for the concrete infra (Postgres, HTTP) separately, injected at the edges.

Research questions

• Is the FastAPI backend's current structure closer to layered MVC or does it separate domain logic from DB/HTTP concerns at all?

---

Empty folder — drop notes, links, and findings here as you research.