Independent deployability hija l-intenzjoni kollha, allura kull servizz jeħtieġ il-pipelines CI/CD tiegħu stess flimkien ma' strateġija ta' release b'riskju baxx — tipikament canary jew blue-green — biex tintbagħat b'mod sigur ħafna drabi kuljum.
Kull servizz jibni, itestja, u jiddeplojja fuq il-cadence tiegħu stess. Bidla għal servizz wieħed qatt ma ttaddi full-system release.
commit ─▶ build ─▶ unit + contract tests ─▶ image ─▶ deploy (one service)
| Strategy | How | Pro | Con |
|---|---|---|---|
| Rolling | Replace instances gradually | Simple, default | Mixed versions briefly |
| Blue-green | Two envs, switch traffic | Instant rollback | 2x infra |
| Canary | Send small % to new version | Limits blast radius | Needs good metrics |
v1 ████████████████ 95% ← watch error rate / latency
v2 █ 5% ← promote if healthy, roll back if not
└─ automated check on SLOs decides promote vs abort
[ Blue v1 ] ◀─ live ──┐
[ Green v2 ] ◀─ idle ├─ flip router ─▶ Green is live; Blue is instant rollback
Bdulenza backward-compatible schemas, canary/blue-green jinqasmu għax żewġ verżjonijiet jduru simultanjament. Dejjem iddisinja bidliet biex ikunu kompatibbli madwar verżjonijiet.
Frequent, low-risk deploys huma dak li jagħmlu microservices ta' sewwa tal-kumplessa — releases bil-mod u b'riskju għaliex jitmerru l-benefiċċju tal-autonomy.
Canary u blue-green jillimitaw ir-riskju ta' bad deploy u jagħtu near-instant rollback, itejbu deployment minn avveniment skariej għal attività rutinarja, awtomatizzata, ta' kuljum.