Skip to content
Back to skills

Arch Decisions

ASecurity

> ADR, database selection ve capacity planning.

  • 18 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 4, 2026
code-qualitygosqlawstestingdebuggingrefactoringgitdatabasedevopsdocumentation

Security analysis

A100/100

Scanned September 4, 2026

npx -y skills add majiayu000/claude-skill-registry-data --skill arch-decisions --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Arch Decisions?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Arch Decisions
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-arch-decisions-claude-skill-registry-data/badge)](https://www.skillsdirectory.com/skills/majiayu000-arch-decisions-claude-skill-registry-data)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: arch-decisions
description: '> ADR, database selection ve capacity planning.'
---

---
name: arch_decisions
router_kit: DevOpsKit
description: ADR template, database selection, capacity planning ve scalability.
metadata:
  skillport:
    category: thinking
    tags: [arch decisions, architecture, automation, best practices, clean code, coding, collaboration, compliance, debugging, design patterns, development, documentation, efficiency, git, optimization, productivity, programming, project management, quality assurance, refactoring, software engineering, standards, testing, utilities, version control, workflow]      - arch-patterns
---

# 📋 Architecture Decisions

> ADR, database selection ve capacity planning.

---

## 📝 ADR Template

```markdown
# ADR-001: Database Selection

## Status: Accepted

## Context
[Problem açıklaması]

## Decision
PostgreSQL kullanacağız.

## Consequences
### Positive
- ACID compliance
### Negative
- Horizontal scaling zor

## Alternatives
- MongoDB: Rejected - JOINs için uygun değil
```

---

## 🗄️ Database Selection

| SQL | NoSQL |
|-----|-------|
| Complex JOINs | Flexible schema |
| ACID | High throughput |
| Transactions | Horizontal scale |

---

## 📊 Capacity Planning

```markdown
DAU: 1M users
Requests: 20/user/day = 20M/day
RPS: 20M / 86400 = ~230 RPS
Peak: 230 × 3 = ~700 RPS
```

---

*Architecture Decisions v1.0*

## 🔄 Workflow

> **Kaynak:** [AWS Architecture Blog](https://aws.amazon.com/blogs/architecture/master-architecture-decision-records-adrs-best-practices-for-effective-decision-making/)

### Aşama 1: Problem Identification
- [ ] **Context**: Problemi ve etkilerini net tanımla.
- [ ] **Constraints**: Kısıtlamaları (Bütçe, Zaman, Teknoloji) belirle.
- [ ] **Options**: En az 2 alternatif çözüm yolu belirle.

### Aşama 2: Proposal (Status: Proposed)
- [ ] **Draft**: ADR şablonunu doldur.
- [ ] **RFC**: Takımdan yorum iste (Pull Request veya Toplantı).
- [ ] **Evaluation**: Alternatifleri kriterlere göre puanla (Pros/Cons).

### Aşama 3: Decision (Status: Accepted/Rejected)
- [ ] **Consensus**: Kararı netleştir ve statüyü güncelle.
- [ ] **Implications**: Kararın uzun vadeli etkilerini (Consequences) yaz.
- [ ] **Commit**: ADR dosyasını repoya ekle.

### Kontrol Noktaları
| Aşama | Doğrulama |
|-------|-----------|
| 1 | Problem ve alternatifler net mi? |
| 2 | Takım görüşü alındı mı? |
| 3 | Kararın "Consequences" bölümü dürüstçe yazıldı mı? |

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…