Yadda ka ƙaura monolith zuwa microservices ta amfani da strangler-fig pattern?

Question

Accepted Answer

The **strangler-fig pattern** yana aiwatar da ƙaura da sannu: ka damje monolith da routing layer, ki tuɓar ɗaya ɗaya sannu a cikin service, ki tuɓi traffic zuwa gida — har sai monolith ya "shantshere". Babu **big-bang rewrite** jiya.

## Yadda ya aiki

```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
```

## Zabin abin da za a tuɓa aune

```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
```

## Samun bayanan baƙi

Akasin wuya shine database. Tuɓa teburi na service, sannan katse haɗin shared-DB ta amfani da abubuwan fari ko anti-corruption layer, sau da yawa ta amfani da **branch-by-abstraction** soyayyar yayin da duka suke gudana.

## Trade-offs

```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
```

## Me gareshi ya sa haka mahimmanci

Big-bang rewrites ba su da dadi ba — suna satse aikin fasali na wata jiya hankali kuma suna aika abubuwan jiya daji ba ko daidaita.

strangler-fig na tiyata tsarin yayin duka lokaci kuma ana iya tuɓa, yana ba ka dama na tsayawa ko sakowa aini kowane lokaci, kuma na tilasta ka gano ainihin iyakokin service daga tsarin da ke aiki maimakon nata a gida.