AgentSkillsCN

system-architect

专家系统架构设计，包括可扩展性、可靠性和分布式系统

SKILL.md
--- frontmatter
name: system-architect
description: Expert system architecture design including scalability, reliability, and distributed systems
version: 1.0.0
author: USER
tags: [architecture, system-design, scalability, distributed, reliability]

System Architect

Purpose

Design robust, scalable system architectures including distributed systems, microservices, and high-availability patterns.

Activation Keywords

  • •system design, architecture
  • •scalability, scale, scaling
  • •distributed system, microservices
  • •reliability, availability, fault tolerance
  • •load balancing, caching, queuing

Core Capabilities

1. System Design Patterns

  • •Monolith vs Microservices
  • •Event-driven architecture
  • •CQRS/Event Sourcing
  • •Saga pattern
  • •Circuit breaker

2. Scalability

  • •Horizontal vs Vertical scaling
  • •Database sharding
  • •Caching strategies
  • •CDN integration
  • •Load balancing

3. Reliability

  • •Redundancy patterns
  • •Failover strategies
  • •Health checks
  • •Graceful degradation
  • •Chaos engineering

4. Communication

  • •Synchronous (REST, gRPC)
  • •Asynchronous (Message queues)
  • •Pub/Sub patterns
  • •API Gateway

5. Data Management

  • •Database selection
  • •Replication strategies
  • •Consistency models (CAP)
  • •Data partitioning

Design Process

code
1. Requirements Analysis
   → Functional requirements
   → Non-functional requirements (scale, latency, availability)
   → Constraints (budget, timeline, team)

2. High-Level Design
   → Component identification
   → Communication patterns
   → Data flow

3. Deep Dive
   → Database design
   → API design
   → Caching strategy

4. Trade-offs
   → Document decisions
   → Identify risks
   → Plan mitigations

Architecture Checklist

markdown
## Non-Functional Requirements
- [ ] Expected QPS/RPS
- [ ] Latency requirements (p50, p99)
- [ ] Availability target (99.9%, 99.99%)
- [ ] Data retention
- [ ] Geographic distribution

## Design Decisions
- [ ] Component boundaries defined
- [ ] Communication protocols chosen
- [ ] Database(s) selected
- [ ] Caching strategy
- [ ] Authentication/Authorization

## Reliability
- [ ] Single points of failure identified
- [ ] Failover strategy
- [ ] Data backup plan
- [ ] Monitoring strategy
- [ ] Alerting defined

Example Usage

code
User: "Design a URL shortener system"

System Architect Response:
1. Requirements
   - 100M URLs created/month
   - 10B redirects/month
   - <100ms redirect latency
   - 99.9% availability

2. High-Level Design
   - API service (stateless)
   - Database (Key-value store)
   - Cache layer (Redis)
   - CDN for popular URLs

3. Data Design
   - Short code generation (Base62)
   - Key-value storage (short_code → original_url)
   - Analytics (separate service)

4. Scale Considerations
   - Database sharding by short_code
   - Cache warming for popular URLs
   - Rate limiting per user