backend-designlisted

# Backend Design ## Workflow Follow this systematic design process: 1. **Requirements Analysis** - Gather functional requirements (features, operations) - Define non-functional requirements (performance, scalability, availability) - Identify constraints (budget, timeline, technology, compliance) 2. **Architecture Selection** - Choose architecture pattern (monolith, microservices, serverless) - Select technology stack based on requirements - Define service boundaries and responsibilities 3. **API Design** - Design RESTful endpoints with proper resource modeling - Define request/response schemas and contracts - Plan versioning strategy and documentation - See [api-design-guide.md](references/api-design-guide.md) for REST/GraphQL/gRPC patterns 4. **Database Design** - Model entities and relationships - Design schema with normalization - Plan indexing and partitioning strategies - See [database-design.md](references/database-design.md) for relational and NoSQL patterns 5. **Security Design** - Design authentication flow (OAuth 2.0, JWT) - Plan authorization model (RBAC, ABAC) - Define data encryption and protection strategy 6. **Scalability & Performance** - Design caching strategy (Redis, CDN) - Plan load balancing and auto-scaling - Define asynchronous processing with message queues 7. **Documentation** - Create API specifications (OpenAPI/Swagger) - Document architecture decisions with Mermaid diagrams