moai-domain-backend

name	moai-domain-backend
description	Backend development specialist covering API design, database integration, microservices architecture, and modern backend patterns. Use when designing APIs, implementing server logic, authentication, or authorization.
when_to_use	Use for backend work: API design (REST, GraphQL, gRPC), server logic, authentication and authorization, microservices, middleware, caching, and frameworks (FastAPI, Express, Django, Flask). Covers serverless, PostgreSQL, MongoDB, and Redis integration.
license	Apache-2.0
compatibility	Designed for Claude Code
allowed-tools	Read, Write, Edit, Bash(npm:*), Bash(npx:*), Bash(node:*), Bash(uv:*), Bash(pip:*), Bash(pytest:*), Bash(ruff:*), Bash(docker:*), Bash(curl:*), Bash(go:*), Bash(cargo:*), Grep, Glob, mcp__context7__resolve-library-id, mcp__context7__get-library-docs
user-invocable	false
metadata	{"version":"1.0.0","category":"domain","status":"active","updated":"2026-01-11","modularized":"false","tags":"backend, api, database, microservices, architecture","author":"MoAI-ADK Team"}

Backend Development Specialist

Quick Reference

Backend Development Mastery - Comprehensive backend development patterns covering API design, database integration, microservices, and modern architecture patterns.

Core Capabilities:

• API Design: REST, GraphQL, gRPC with OpenAPI 3.1
• Database Integration: PostgreSQL, MongoDB, Redis, caching strategies
• Microservices: Service mesh, distributed patterns, event-driven architecture
• Security: Authentication, authorization, OWASP compliance
• Performance: Caching, optimization, monitoring, scaling

When to Use:

• Backend API development and architecture
• Database design and optimization
• Microservices implementation
• Performance optimization and scaling
• Security integration for backend systems

---

Implementation Guide

API Design Patterns

RESTful API Architecture:

Create a FastAPI application with authentication and response models. Define a Pydantic UserResponse model with id, email, and name fields. Implement list_users and create_user endpoints with HTTPBearer security dependency. The list endpoint returns a list of UserResponse objects, while the create endpoint accepts a UserCreate model and returns a single UserResponse.

GraphQL Implementation:

Use Strawberry to define GraphQL types. Create a User type with id, email, and name fields. Define a Query type with a users resolver that returns a list of User objects asynchronously. Generate the schema by passing the Query type to strawberry.Schema.

Database Integration Patterns

PostgreSQL with SQLAlchemy:

Define SQLAlchemy models using declarative_base. Create a User model with id as primary key, email as unique string, and name as string column. Configure the engine with connection pooling parameters including pool_size of 20, max_overflow of 30, and pool_pre_ping enabled for connection health checks.

MongoDB with Motor:

Create a UserService class that initializes with an AsyncIOMotorClient. Set up the database and users collection in the constructor. Create indexes for email (unique) and created_at fields. Implement create_user method that inserts a document and returns the inserted_id as string.

Microservices Architecture

Service Discovery with Consul:

Create a ServiceRegistry class that connects to Consul. Implement register_service method that registers a service with name, id, port, and health check endpoint. Implement discover_service method that queries healthy services and returns list of adddess:port strings.

Event-Driven Architecture:

Create an EventBus class using aio_pika for AMQP messaging. Implement connect method to establish connection and channel. Implement publish_event method that serializes event type and data as JSON and publishes to the default exchange with routing_key matching the event type.

---

Advanced Patterns

Caching Strategies

Redis Integration:

Create a CacheManager class with Redis connection. Implement a cache_result decorator that accepts ttl parameter. The decorator generates cache keys from function name and arguments, checks Redis for cached results, executes the function on cache miss, and stores results with expiration. Use json.loads and json.dumps for serialization.

Security Implementation

JWT Authentication:

Create a SecurityManager class with CryptContext for bcrypt password hashing. Implement hash_password and verify_password methods using the context. Implement create_access_token that encodes a JWT with expiration time using HS256 algorithm. Default expiration is 15 minutes if not specified.

Performance Optimization

Database Connection Pooling:

Create an optimized SQLAlchemy engine with QueuePool, pool_size 20, max_overflow 30, pool_pre_ping enabled, and pool_recycle of 3600 seconds. Add event listeners for before_cursor_execute and after_cursor_execute to track query timing. Log warnings for queries exceeding 100ms threshold.

---

Works Well With

• moai-domain-frontend - Full-stack development integration
• moai-domain-database - Advanced database patterns
• moai-foundation-core - MCP server development patterns for backend services
• moai-foundation-quality + moai-ref-owasp-checklist - Security validation and compliance
• moai-foundation-core - Core architectural principles

---

Technology Stack

Primary Technologies:

• Languages: Python 3.13+, Node.js 20+, Go 1.23
• Frameworks: FastAPI, Django, Express.js, Gin
• Databases: PostgreSQL 16+, MongoDB 7+, Redis 7+
• Message Queues: RabbitMQ, Apache Kafka, Redis Pub/Sub
• Containerization: Docker, Kubernetes
• Monitoring: Prometheus, Grafana, OpenTelemetry

Integration Patterns:

• RESTful APIs with OpenAPI 3.1
• GraphQL with Apollo Federation
• gRPC for high-performance services
• Event-driven architecture with CQRS
• API Gateway patterns
• Circuit breakers and resilience patterns

---

Resources

For working code examples, see examples.md.

Status: Production Ready Last Updated: 2026-01-11 Maintained by: MoAI-ADK Backend Team

Common Rationalizations

Rationalization	Reality
"Input validation can happen on the frontend"	Frontend validation is UX. Backend validation is security. They serve different purposes and both are required.
"This endpoint is internal, it does not need authentication"	Internal endpoints are reachable from compromised services. Zero-trust means every endpoint validates identity.
"I will add error handling later"	Unhandled errors leak stack traces, connection strings, and internal state. Error handling is day-one work.
"The ORM handles SQL injection"	ORMs protect parameterized queries. Raw queries, dynamic filters, and ORDER BY clauses still need escaping.
"This API is backward-compatible, no version bump needed"	Removing optional fields, changing defaults, or altering error formats are breaking changes to existing callers.
"Microservices are overkill, I will just add another endpoint"	Unbounded endpoint growth creates a monolith-in-disguise. Evaluate service boundaries before adding.

Hyrum's Law: With a sufficient number of users, every observable behavior of your API will be depended on by somebody. Changing anything, no matter how trivial, can break someone.

Red Flags

• API endpoint accepts user input without validation or sanitization
• Error response includes stack trace or internal path information
• Database credentials hardcoded in source code instead of environment variables
• No rate limiting configured on public-facing endpoints
• API returns 200 OK for every failure case with error in the response body
• Raw SQL queries built with string concatenation

Verification

• Every endpoint validates input before processing (show validation middleware or checks)
• Error responses use standard format without internal details (show sample error response)
• Credentials sourced from environment variables, not config files (grep for hardcoded secrets)
• Rate limiting configured on public endpoints (show middleware registration)
• API versioning strategy documented and enforced
• Database queries use parameterized statements (no string concatenation with user input)
• Authentication required on all non-public endpoints (show auth middleware)

Refactor Notes

Refactor scope (deferred to future sub-SPEC):

• Narrow body to API design decision matrix (REST vs GraphQL vs tRPC vs gRPC)
• Extract language-specific implementation details into Level-3 modules
• Remove framework-specific content that duplicates language skill coverage

This skill is retained in v3.0 but its body will be restructured in a follow-up SPEC.