moai-domain-backend-reference

Guide backend architecture decisions for cloud-native APIs and infrastructure.

1|Updated Jul 28, 2025

Search Tags:#architecture #backend #microservices #monolith

Ready to run

npx skills add https://github.com/kivo360/quickhooks --skill moai-domain-backend-reference

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: moai-domain-backend-reference
Source: https://github.com/kivo360/quickhooks/tree/main/.claude/skills/moai-domain-backend/reference.md
Command: npx skills add https://github.com/kivo360/quickhooks --skill moai-domain-backend-reference

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill references backend architecture decisions and patterns with detailed guidance.

Core Features & Use Cases

Decision Matrix: When to choose monolith vs microservices.
Patterns: Layered, modular monolith, event-driven approaches.

Quick Start

Review the decision matrix before starting a backend project.

Frequently Asked Questions about moai-domain-backend-reference

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I decide between a monolith and microservices architecture?▼

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.

What backend patterns work best for scaling server-side APIs?▼

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.

How do I design APIs for cloud-native and microservices environments?▼

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.

What caching and database optimization strategies reduce backend latency?▼

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.

Can I use these patterns with serverless and event-driven architectures?▼

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.

What security practices should I follow for backend APIs?▼

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.