🎁 New User? Get 20% off your first purchase with code NEWUSER20 Register Now →
Menu

Categories

DevOps Intermediate

What is Trunk-Based Development?

A source control strategy where developers integrate small changes directly into the main branch frequently, often multiple times per day.

Trunk-based development minimizes merge conflicts and enables continuous integration by having all developers commit to a single shared branch (trunk/main). Short-lived feature branches (lasting hours, not days) are permitted but must merge quickly. This approach requires strong automated testing, feature flags for incomplete work, and code review practices. It enables continuous deployment since the trunk is always in a deployable state. Google, Facebook, and other tech giants practice trunk-based development at massive scale. It contrasts with GitFlow where long-lived branches can diverge significantly.

Related Terms

Blue-Green Deployment
A deployment strategy using two identical environments where traffic is switched from the old version to the new one instantly.
Grafana
An open-source analytics and visualization platform for creating dashboards from various data sources.
Container Registry
A storage and distribution service for container images, similar to a package repository but for Docker images.
SonarQube
A platform for continuous code quality inspection that detects bugs, vulnerabilities, and code smells through static analysis.
Runbook
A documented set of standardized procedures for handling routine operations and incident response in production systems.
Service Discovery
A mechanism that automatically detects and tracks the network locations of service instances in distributed systems.
View All DevOps Terms →