Trunk-Based Development vs Long-Lived Branches
Design a small subsystem that relies on Trunk-Based Development vs Long-Lived Branches. Outline components, data flow, failure modes, and metrics.
Answers use simple, clear English.
Audio N/AQuick interview answer
Use Trunk-Based Development vs Long-Lived Branches as the core idea. Example shape: Team merges daily to main; dark-launches checkout redesign behind flag..
Detailed answer
Use Trunk-Based Development vs Long-Lived Branches as the core idea. Example shape: Team merges daily to main; dark-launches checkout redesign behind flag.. Watch for: Needs solid CI and flag discipline.. Measure success via latency/error/saturation. Core: Short-lived branches merge to main frequently; feature flags hide incomplete work. Long-lived release branches increase merge pain and drift. Real-time example: Team merges daily to main; dark-launches checkout redesign behind flag. Pros: Smaller PRs; continuous integration truly continuous. Cons: Needs solid CI and flag discipline. Common mistakes: Week-long feature branches without syncing main. Best practices: Required checks; small PRs; flags for incomplete features. Audience level: Tech Lead.
Full explanation
Short-lived branches merge to main frequently; feature flags hide incomplete work. Long-lived release branches increase merge pain and drift.
Real example & use case
Team merges daily to main; dark-launches checkout redesign behind flag.
Pros & cons
Pros: Smaller PRs; continuous integration truly continuous. Cons: Needs solid CI and flag discipline.
Common mistakes
Week-long feature branches without syncing main.
Best practices
Required checks; small PRs; flags for incomplete features.
Follow-up questions
Open one as its own read / solve / listen card