arch_patterns
Architecture patterns - monolith vs microservices, layered, event-driven, CQRS.
Best use case
arch_patterns is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Architecture patterns - monolith vs microservices, layered, event-driven, CQRS.
Teams using arch_patterns should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/arch_patterns/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How arch_patterns Compares
| Feature / Agent | arch_patterns | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Architecture patterns - monolith vs microservices, layered, event-driven, CQRS.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 🏗️ Architecture Patterns
> Sistem mimarisi pattern'ları.
---
## ⚠️ Bu Skill vs `design-patterns`
| Bu Skill | `design-patterns` |
|----------|-------------------|
| **Sistem** mimarisi | **UI/UX** tasarım |
| Microservices, CQRS | Z-index, shadows |
| Database, scaling | Animation, spacing |
> **Kural:** Backend/sistem → bu skill, Frontend/UI → `design-patterns`
---
## ⚖️ Monolith vs Microservices
| Aspect | Monolith | Microservices |
|--------|----------|---------------|
| Complexity | Düşük | Yüksek |
| Scaling | Tüm uygulama | Service bazlı |
| Team Size | Küçük | Büyük |
**Seç:**
- Monolith: Küçük takım, MVP, hızlı iteration
- Microservices: Büyük takım, bağımsız deploy
---
## 📚 Layered Architecture
```
Presentation → Application → Domain → Infrastructure
```
---
## ⚡ Event-Driven
```
Producer → Event Broker → Consumer
(Kafka/SQS)
```
---
## 📊 CQRS
```
Command Service → Write DB
↓ Events
Query Service ← Read DB
```
---
## 🧩 Modular Monolith
```
Modules separated by boundaries within a single deployable unit.
Good for: Teams growing from startup to scale-up phase.
Prevents "Distributed Monolith" chaos.
```
---
*Architecture Patterns v1.1 - Enhanced*
## 🔄 Workflow
> **Kaynak:** [Software Architecture Guide](https://martinfowler.com/architecture/)
### Aşama 1: Requirements Analysis
- [ ] **Functional**: Ne yapacak? (E-ticaret, Blog, IoT)
- [ ] **Non-Functional**: Scalability, Latency, Consistency ihtiyacı.
- [ ] **Constraints**: Takım boyutu, bütçe, timeline.
### Aşama 2: Complexity Assesment
- [ ] **Domain Complexity**: Karmaşıksa -> DDD + Layered/Hexagonal.
- [ ] **Scale Complexity**: Yüksek trafik -> Event-Driven / Microservices.
- [ ] **Data Complexity**: Raporlama ağırsa -> CQRS.
### Aşama 3: Pattern Selection
- [ ] **Default**: Modular Monolith ile başla.
- [ ] **Scale-out**: Bağımsız scale gereken modülleri ayır (Microservices).
- [ ] **Real-time**: Event-Driven ekle.
### Kontrol Noktaları
| Aşama | Doğrulama |
|-------|-----------|
| 1 | Gereksinimler net (NFRs belirlendi) |
| 2 | Seçilen pattern probleme uygun (Over-engineering değil) |
| 3 | Takım bu mimariyi yönetebilir |Related Skills
backend-architecture
Design and implement scalable backend infrastructure, microservices, and system architecture patterns.
backend-architect
Expert backend architect specializing in scalable API design, microservices architecture, and distributed systems. Masters REST/GraphQL/gRPC APIs, event-driven architectures, service mesh patterns, and modern backend frameworks. Handles service boundary definition, inter-service communication, resilience patterns, and observability. Use PROACTIVELY when creating new backend services or APIs.
azure-search-documents-ts
Build search applications using Azure AI Search SDK for JavaScript (@azure/search-documents). Use when creating/managing indexes, implementing vector/hybrid search, semantic ranking, or building ag...
atlan-sql-connector-patterns
Select and apply the correct SQL connector implementation pattern (SDK-default minimal or source-specific custom). Use when building or extending SQL metadata/query extraction connectors.
asyncio-concurrency-patterns
Complete guide for asyncio concurrency patterns including event loops, coroutines, tasks, futures, async context managers, and performance optimization
async-python-patterns
Master Python asyncio, concurrent programming, and async/await patterns for high-performance applications. Use when building async APIs, concurrent systems, or I/O-bound applications requiring non-blocking operations.
async-patterns-guide
Guides users on modern async patterns including native async fn in traits, async closures, and avoiding async-trait when possible. Activates when users work with async code.
async-await-patterns
Use when writing JavaScript or TypeScript code with asynchronous operations
astro-patterns
Astro best practices, routing patterns, component architecture, and static site generation techniques. Use when building Astro websites, setting up routing, designing component architecture, configuring static site generation, optimizing build performance, implementing content strategies, or when user mentions Astro patterns, routing, component design, SSG, static sites, or Astro best practices.
astro-architecture
Technical architecture for Astro lead generation websites. Use when setting up new projects, configuring build tools, or establishing project foundations. For images use astro-images skill. For SEO use astro-seo skill.
assessment-architect
Generate certification exams for chapters or parts. Extracts concepts first, then generates scenario-based questions. Use "ch X" for chapter, "part X" for part.
assessing-architecture-quality
Use when assessing codebase architecture and you feel pressure to soften critique, lead with strengths, or frame problems diplomatically - provides evidence-based critical assessment resisting relationship and economic pressures