baasith6/cursor-skills/architecture-decision-records

# ADR-001: Use PostgreSQL for primary database
 
## Status
 
Accepted | Proposed | Deprecated | Superseded by ADR-XXX
 
## Date
 
2026-04-10
 
## Context
 
What is the problem or situation that requires a decision?
Include constraints, requirements, and forces at play.
 
## Options Considered
 
### Option A: PostgreSQL
-Pros: ACID compliance, JSON support, mature ecosystem, free
-Cons: Requires managing connections, vertical scaling limits
 
### Option B: MongoDB
-Pros: Flexible schema, horizontal scaling
-Cons: No transactions across collections, eventual consistency issues
 
### Option C: PlanetScale (MySQL)
-Pros: Serverless, branching, managed
-Cons: Vendor lock-in, no foreign keys in their branching model
 
## Decision
 
We chose **PostgreSQL** because:
1.Our data is relational — users, teams, projects with clear relationships
2.We need ACID transactions for billing operations
3.JSON columns give us schema flexibility where needed
4.Prisma/Drizzle have excellent Postgres support
 
## Consequences
 
-We need to manage connection pooling (use PgBouncer or Prisma's built-in pool)
-Migrations must be backwards-compatible for zero-downtime deploys
-We accept vertical scaling limits and will shard later if needed

docs/decisions/
├── 001-use-postgresql.md
├── 002-adopt-trpc-over-rest.md
├── 003-switch-to-pnpm.md
└── template.md