Piye carane migrasi monolith menyang microservices nggunakake strangler-fig pattern?

Question

Accepted Answer

**Strangler-fig pattern** migrasi kanthi bertahap: sampeyan ngumpal monolith karo routing layer, ngetok kemampuan siji-siji menyang service, lan ngarahake traffic — nganti monolith "singset". **Ora ana rewrite big-bang**.

## Carane kerja

```text
Step 1: route all traffic through a facade/proxy to the monolith
Step 2: extract ONE capability → new service
Step 3: route just that path to the new service
Step 4: repeat; delete that code from the monolith

Client ─▶ [ Proxy ] ─┬─▶ /orders  ─▶ NEW Orders service
                       └─▶ everything else ─▶ Monolith
```

## Milih apa sing kudu diekstrak rumiyin

```text
✓ A bounded context with clear boundaries
✓ Something that needs independent scaling or deploys
✓ A part with few inbound dependencies (low risk)
✗ Don't start with the tangled core
```

## Nangani data sing dibagiake

Bagean sing angel yaiku database. Ekstrak tabel service, banjur putus coupling database sing dibagiake nggunakake events utawa anti-corruption layer, asring nggunakake teknik **branch-by-abstraction** nalika loro-lorone running.

## Trade-off

```text
✓ Low risk — small, reversible steps, always shippable
✓ Value early, learn the seams as you go
✗ Slow; you run a hybrid system for a long time
✗ Temporary duplication and routing complexity
```

## Apa sing penting

Rewrite big-bang misuwur-misuwur gagal — padha mbeku feature work saperlu sasi lan shipping cutover sing riskful kabeh saatungan.

Strangler-fig tetep sistem live lan releasable kabeh waktune, ngidini sampeyan mandheg utawa reprioritisasi kapan wae, lan maksa sampeyan nemokake batas service nyata saka sistem sing running tinimbang ngarang-arang ing mBlanyu.