Social Network Kata Documentation

A small, Docker-packaged social-network backend kata built test-first across three bounded contexts — Users, Posts/Timeline, and Messaging. This site collects the architecture documentation (arc42) and the user-story bundles that drive the TDD/BDD cycle.

Overview:

• Social Network Kata
  • What the kata solves
  • Tech stack
  • Architecture overview
  • Build and run
  • Run tests locally (without Docker)
  • Project structure
  • Documentation
  • License
  • Author

Architecture:

• 1. Introduction and Goals
  • 1.1 Requirements Overview
  • 1.2 Quality Goals
  • 1.3 Stakeholders
  • 1.4 System Context
• 2. Constraints
  • 2.1 Technical Constraints
  • 2.2 Organisational Constraints
  • 2.3 Conventions
• 3. Context and Scope
  • 3.1 Business Context
  • 3.2 Technical Context
  • 3.3 Bounded Context Map
• 4. Solution Strategy
  • 4.1 Fundamental Decisions
  • 4.2 Architecture Style
  • 4.3 Key Technology Decisions
  • 4.4 How the Strategy Meets the Quality Goals
• 5. Building Block View
  • 5.1 Level 1 — Containers
  • 5.2 Level 2 — Internal Structure per Service
  • 5.3 Cross-Context Interfaces
• 6. Runtime View
  • 6.1 User Registration and Login
  • 6.2 Post Creation
  • 6.3 Timeline Feed (Fan-out on Read)
  • 6.4 Send Direct Message
  • 6.5 Mention Flow
  • 6.6 JWT Validation (all services)
• 7. Deployment View
  • 7.1 Deployment Topology
  • 7.2 Infrastructure Components
  • 7.3 Routing Rules (nginx)
  • 7.4 Environment Configuration
  • 7.5 Dev vs Production
• 8. Cross-Cutting Concepts
  • 8.1 Authentication & Authorisation
  • 8.2 Error Handling
  • 8.3 Logging
  • 8.4 Observability
  • 8.5 Input Validation
  • 8.6 Database Migrations
  • 8.7 CORS
  • 8.8 Rate Limiting
• 9. Architecture Decisions
  • ADR-001: FastAPI as the Web Framework
  • ADR-002: One PostgreSQL Schema per Bounded Context
  • ADR-003: JWT RS256 for Authentication
  • ADR-004: Fan-out on Read for Timeline Feed
  • ADR-005: Modular Monorepo over Microservices
• 10. Quality Requirements
  • 10.1 Quality Tree
  • 10.2 Quality Scenarios
• 11. Risks and Technical Debts
  • 11.1 Risks
  • 11.2 Technical Debts
• 12. Glossary

User Stories:

• User Stories — Social Network Kata
  • Pareto Progress
  • API Route Convention
  • Story Inventory
  • Pareto Rationale
  • Story Files
• Users Domain — Story Bundles
  • USER-STORY-001 — Register an account ✅ [CORE]
  • USER-STORY-002 — Log in and receive a JWT ✅ [Supporting]
  • USER-STORY-003 — View and edit own profile ✅ [Supporting]
  • USER-STORY-004 — Follow / unfollow another user ✅ [Supporting]
  • USER-STORY-005 — List followers / followees ✅ [Supporting]
• Posts / Timeline Domain — Story Bundles
  • POST-STORY-001 — Create a post ✅ [CORE]
  • POST-STORY-002 — Read aggregated timeline feed ✅ [CORE]
  • POST-STORY-003 — Like / unlike a post ✅ [Supporting]
  • POST-STORY-004 — Edit / delete own post ✅ [Supporting]
• Messaging Domain — Story Bundles
  • MSG-STORY-001 — Send a direct message ✅ [Supporting]
  • MSG-STORY-002 — Read a conversation ✅ [Supporting]
  • MSG-STORY-003 — Mention a user in a message ✅ [Supporting]

Indices and tables

• Index

• Search Page