moai-domain-backend-reference

Monolith vs microservices depends on team size, deployment frequency, and scaling needs. Use the decision matrix to evaluate trade-offs: monoliths simplify initial development and deployment; microservices enable independent scaling and team autonomy but add operational complexity. Choose based on your current constraints.

Layered, modular monolith, and event-driven patterns each suit different scaling scenarios. Layered architectures isolate concerns; modular monoliths defer microservice migration; event-driven systems decouple services for async processing. Select the pattern matching your team capability and infrastructure maturity.

RESTful and GraphQL API design align with cloud-native deployment models. Ensure service layering, API orchestration, and caching strategies match your infrastructure—Kubernetes, Istio, and observability tooling like OpenTelemetry. Apply OWASP API Top 10 security practices throughout.

Caching strategies and database optimization are core to backend scaling. Implement layered caching, optimize queries, and tune connection pooling. Pair with observability via OpenTelemetry to measure impact and identify bottlenecks in your service architecture.

Yes. Layered, microservice, and event-driven patterns adapt to serverless and event-driven contexts. The guidance covers background processing, service decoupling, and API design for these models. Adjust caching and database strategies for stateless function execution.

Align API design and service layering with OWASP API Top 10 security requirements. Implement authentication, authorization, input validation, and rate limiting across service boundaries. Security is part of the architecture decision matrix, not an afterthought.