Sepira Conway's Law lan topologi tim mbentuk microservices?

Question

Accepted Answer

Microservices minangka kaputusan **organisasi** kaya kaputusan teknis. **Conway's Law** nyatakna yen sistem nglambari struktur komunikasi organisasi kang mbangun — dadi struktur tim mu bentuka arsitektur mu, bakal or ora sampeyan rencanakna.

## Kenapa iku penting

```text
"Organizations design systems that copy their communication structure."

3 teams that don't talk  →  3 services with awkward, accidental seams
→ Inverse Conway Maneuver: design TEAMS around the architecture you want
```

## Ownership tim

Saben layanan kudu duweni **tim pemilik sing jelas** kang bangun, deploy, lan operate ("kowe bangun, kowe operate"). Ownership bareng nyebabna layanan dilalekna.

```text
Orders team   ─owns─▶ Orders service (code + deploy + on-call)
Payments team ─owns─▶ Payments service
→ autonomy: each team ships without waiting on others
```

## Team Topologies

| Jenis tim | Peran |
|---|---|
| Stream-aligned | Gawe bagian produk (umume tim) |
| Platform | Nyedhiyakna infra self-service (CI/CD, mesh) |
| Enabling | Ngedidik tim liyane praktik |
| Complicated-subsystem | Gawe area khusus sing jereng |

Tujuan mau yaiku ngurangi **beban kognitif** lintas-tim lan serah-terima.

## Jebakan

Sinau microservices tanpa nguwarakna tim nyebabna monolith terdistribusi, amarga pola koordinasi lawas nyorot menyang arsitektur.

## Kenapa iku penting

Yen tim kudu terus koordinasi kanggo ngirim siji fitur, arsitektur bakal nglambari coupling iku utawa ora sampeyan gambar diagram layanan kanthi jelas.

Mdherekna wates tim karo wates layanan (maneuver Conway invers) apa kang bener nyedhiyakna otonomi lan keuntungan deploy-mandiri kang microservices tebusna — bagan organisasi dadi bagian saka design.

Jenis tim	Peran
Stream-aligned	Gawe bagian produk (umume tim)
Platform	Nyedhiyakna infra self-service (CI/CD, mesh)
Enabling	Ngedidik tim liyane praktik
Complicated-subsystem	Gawe area khusus sing jereng