System Design
System Design Skill
Purpose
Enable the Solution Architect Agent to design the high-level structure of software systems, selecting appropriate patterns, technologies, and integration strategies.
Architectural Patterns
1. Monolithic
- Use Case: Small startup, simple domain, fast initial dev.
- Pros: Simple deployment, easy debugging.
- Cons: Scalability limits, tight coupling.
2. Microservices
- Use Case: Complex enterprise, distinct domains, independent scaling.
- Pros: Tech stack agnostic per service, scalable.
- Cons: Distributed complexity, network latency, data consistency.
3. Event-Driven
- Use Case: Real-time interactions, high decoupling.
More from danhvb/my-ba-skills
erp domain knowledge
Understand ERP systems covering Finance, HR, Supply Chain, Manufacturing, and Procurement modules for enterprise implementations
105e-commerce domain knowledge
Understand e-commerce business models, core modules, and requirements patterns for B2C, B2B, C2C, and Marketplace platforms
90crm domain knowledge
Understand CRM systems covering Sales, Marketing, and Customer Service modules for lead management, pipeline tracking, and customer engagement
39process mapping
Create clear business process diagrams using BPMN, flowcharts, and swimlane diagrams for Web, Mobile, ERP, CRM, CDP, and E-commerce projects
34requirements elicitation
Guide AI assistants in conducting effective requirements gathering sessions using proven techniques for Web, Mobile, ERP, CRM, CDP, and E-commerce projects
34brd creation
Guide AI assistants in creating professional Business Requirement Documents for Web, Mobile, ERP, CRM, CDP, and E-commerce projects
33