Follow-up · depth 10
How do you make Trunk-Based Development vs Long-Lived Branches safer under partial failure?
How do you make Trunk-Based Development vs Long-Lived Branches safer under partial failure?
Answers use simple, clear English.
Quick interview answer
Harden Trunk-Based Development vs Long-Lived Branches with timeouts, retries with jitter, isolation, and graceful degradation. Simple view: Short-lived branches merge to main frequently; feature flags hide incomplete work. Long-lived release branches increase merge pain and drift.
Detailed answer
Resilience for Trunk-Based Development vs Long-Lived Branches under partial failure: • Timeouts + budgets on every dependency call • Retries only when idempotent, with jitter/backoff • Isolation: bulkheads/queues so one failure does not cascade • Degradation: serve stale/cached/limited mode when needed Practices: Required checks; small PRs; flags for incomplete features. Parent context: Simple view: Short-lived branches merge to main frequently; feature flags hide incomplete work. Long-lived release branches increase merge pain and drift.
Full explanation
Partial failure is the default in distributed systems — show how Trunk-Based Development vs Long-Lived Branches stays useful anyway. Short-lived branches merge to main frequently; feature flags hide incomplete work. Long-lived release branches increase merge pain and drift.
Follow-up questions
Only answered follow-ups are shown — click to open with full answers
Parent context — Trunk-Based Development vs Long-Lived Branches
Simple view: Short-lived branches merge to main frequently; feature flags hide incomplete work. Long-lived release branches increase merge pain and drift.
View full parent question →