菜单
Master architectural design with SOLID principles, design patterns, microservices, and event-driven systems. Learn to design scalable backend systems.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/pluginagentmarketplace/custom-plugin-backend --skill architecture命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Design and build professional APIs with REST, GraphQL, and gRPC. Master authentication, documentation, testing, and operational concerns.
Backend authentication and authorization patterns. JWT, OAuth2, session management, RBAC, and secure token handling.
Master relational and NoSQL databases. Learn PostgreSQL, MySQL, MongoDB, Redis, and other technologies for data persistence, optimization, and scaling.
基于 SOC 职业分类
正在显示 SKILL.md
| name | architecture |
| description | Master architectural design with SOLID principles, design patterns, microservices, and event-driven systems. Learn to design scalable backend systems. |
| sasmp_version | 2.0.0 |
| bonded_agent | 04-architecture-patterns |
| bond_type | PRIMARY_BOND |
| atomic_operations | ["PATTERN_SELECTION","ARCHITECTURE_DESIGN","SERVICE_DECOMPOSITION","TRADE_OFF_ANALYSIS"] |
| parameter_validation | {"query":{"type":"string","required":true,"minLength":5,"maxLength":3000},"architecture_type":{"type":"string","enum":["monolith","microservices","serverless","event-driven"],"required":false},"scale":{"type":"string","enum":["startup","growth","enterprise"],"required":false}} |
| retry_logic | {"max_attempts":2,"backoff":"exponential","initial_delay_ms":2000} |
| logging_hooks | {"on_invoke":"skill.architecture.invoked","on_success":"skill.architecture.completed","on_error":"skill.architecture.failed"} |
| exit_codes | {"SUCCESS":0,"INVALID_INPUT":1,"OVER_ENGINEERING":2,"ANTI_PATTERN_DETECTED":3} |
Bonded to: architecture-patterns-agent
# Invoke architecture skill
"Help me decompose this monolith into microservices"
"Which design pattern should I use for notifications?"
"Design an event-driven architecture for order processing"
| Style | Best For | Team Size | Complexity | Scale |
|---|---|---|---|---|
| Monolith | MVPs, small teams | 1-10 | Low | Vertical |
| Modular Monolith | Growing apps | 5-20 | Medium | Vertical |
| Microservices | Large teams | 20+ | High | Horizontal |
| Serverless | Variable load | 1-15 | Medium | Auto |
| Event-Driven | Real-time, async | 10+ | High | Horizontal |
Team size & complexity?
│
├─→ Small team (1-5) → Monolith
│
├─→ Growing team (5-20)
│ ├─→ Clear domain boundaries → Modular Monolith
│ └─→ Variable load → Serverless
│
└─→ Large team (20+)
├─→ Real-time/async heavy → Event-Driven
└─→ Independent scaling needed → Microservices
| Principle | Description | Violation Sign |
|---|---|---|
| Single Responsibility | One reason to change |
| Class does too many things |
| Open/Closed | Open for extension, closed for mod | Editing existing code for new features |
| Liskov Substitution | Subtypes substitutable | Subclass changes behavior unexpectedly |
| Interface Segregation | Small, specific interfaces | Clients implement unused methods |
| Dependency Inversion | Depend on abstractions | High-level depends on low-level |
| Pattern | Use Case |
|---|---|
| Singleton | Global config, connection pools |
| Factory | Object creation with logic |
| Builder | Complex object construction |
| Pattern | Use Case |
|---|---|
| Adapter | Interface compatibility |
| Decorator | Dynamic behavior extension |
| Facade | Simplified interface |
| Proxy | Access control, caching |
| Pattern | Use Case |
|---|---|
| Observer | Event notifications |
| Strategy | Algorithm selection |
| Command | Action encapsulation |
| State | State machines |
E-commerce Monolith → Microservices
Services:
├── user-service (auth, profiles)
├── product-service (catalog, inventory)
├── order-service (orders, checkout)
├── payment-service (transactions)
├── notification-service (email, push)
└── api-gateway (routing, auth)
Communication:
├── Sync: REST/gRPC for queries
└── Async: Event bus for commands/events
from abc import ABC, abstractmethod
from typing import List
class Observer(ABC):
@abstractmethod
def update(self, event: dict) -> None:
pass
class NotificationService:
def __init__(self):
self._observers: List[Observer] = []
def subscribe(self, observer: Observer) -> None:
self._observers.append(observer)
def notify(self, event: dict) -> None:
for observer in self._observers:
observer.update(event)
class EmailHandler(Observer):
def update(self, event: dict) -> None:
send_email(event["user_id"], event["message"])
class PushHandler(Observer):
def update(self, event: dict) -> None:
send_push(event["user_id"], event["message"])
# Saga pattern for order processing
class OrderSaga:
async def process_order(self, order_id: str):
try:
# Step 1: Reserve inventory
await self.inventory_service.reserve(order_id)
# Step 2: Process payment
await self.payment_service.charge(order_id)
# Step 3: Confirm order
await self.order_service.confirm(order_id)
except PaymentError:
# Compensating transaction
await self.inventory_service.release(order_id)
await self.order_service.cancel(order_id)
raise
| Anti-Pattern | Sign | Solution |
|---|---|---|
| Distributed Monolith | Services too coupled | Define bounded contexts |
| God Class | One class does everything | Extract by responsibility |
| Circular Dependencies | A→B→C→A | Introduce interfaces |
| Shared Database | Multiple services, one DB | Database per service |
# tests/test_architecture.py
import pytest
class TestServiceBoundaries:
def test_services_are_independent(self):
# Each service should work independently
user_service = UserService()
order_service = OrderService()
# Services communicate via events/APIs, not direct calls
assert not hasattr(order_service, 'user_repository')
def test_no_circular_dependencies(self):
from app.services import dependency_graph
cycles = dependency_graph.find_cycles()
assert len(cycles) == 0
See references/ directory for:
ARCHITECTURE_GUIDE.md - Detailed patternsdesign-patterns.yaml - Pattern catalog