Continuous delivery best practices
Successful teams implementing continuous delivery observe a set of best practices that lead to small, autonomous changes that are delivered to users rapidly and reliably.
A key tenet of continuous delivery is reducing batch size. By slimming down the amount of code deployed and released, and adopting processes like trunk-based development, you’ll speed up deployment and reduce risk.
Continuous delivery also emphasizes sustainable development by closing the feedback loop from users to developers.
Extending continuous delivery to feature delivery
Split brings continuous delivery best practices to software development teams, supporting trunk-based development and easy coordination across microservices.
Feature flags give development teams the tools to deploy often and release changes when they’re ready. Automated alerts notify responsible teams to error spikes or service level degradation, reducing the release risk.
Split also measures the impact of each change, from new features to backend configurations, closing the feedback loop to support sustainable development.