Separate Code Deployment From Feature Release
Why Feature Flags?
As engineering teams increasingly adopt continuous delivery best practices, many find that there is a gap in how to manage the customer experience. Feature flags, or feature toggles, are a best practice that solves the problem of controlling the user experience, while still empowering developers to integrate code as soon as it is ready to deploy.
As a key enabling technology for continuous delivery, Split solves the feature flag gap. And, Split goes beyond simple on/off feature toggling, providing granular targeting capabilities to expose a feature to exactly the right users, based on any attribute and with sophisticated regex matching. This enables more comprehensive feature management and gives product teams the flexibility to ensure exactly the right user experience.
“Without Split, rollbacks could take a couple hours to a day. And after that, there might still be a lot of code cleanup. Split helped us increase our engineering velocity and code stability.”Drew Newberry, Senior Software Engineering Manager
“We wanted something that was easy to work with,Dan DeMeyere, VP Engineering
developer friendly, had an intuitive UI, and had everything
we needed from a data standpoint. Split just had
everything we needed out of the box.”
“We don’t like to spend time doing things that aren’tChris Conrad, VP Engineering
our core competency. Why maintain a feature flagging system,
build and maintain its UI, or monitor its performance? Split does what we need it to do, and any engineer in the company can use it.”
“Split’s controlled release capability provides us a non-disruptiveQingqing Ouyang, SVP Engineering
and dynamic way to ship features for testing and deployment.
More importantly, it provides the data we need to quickly iterate on
our product features in an informed manner.”
Release Features Faster with Less Risk
Split enables feature flag driven deployment and helps engineering teams control
what code executes or stays hidden for end users.
Global User Segments
Define groups that can be used in whitelists in any feature definition. Typically used to define beta users, VIP customers, or internal employees.
Be extremely specific in selecting the customers to be included in a release by custom segments, real-time attributes or percentage.
Full-Stack Feature Control
Manage features anywhere in your codebase, across any language, and deliver in any deployment environment.
Multi-Variate Feature Flags
Manage and control whether segments of code execute for end-users, and define multiple treatments (i.e. variations) of a feature. Configure any number of treatments.
Disable problematic code while keeping the rest of the feature release intact.
Create focused on/off feature release plans or release multiple versions of the same feature all at once.
Track every change that takes place, who made them, and what exactly was added or removed from your feature configuration.
Traffic Type Definition
Configure multiple ways for an app to identify a user to Split to determine what version of a feature to show. For example, B2B companies can target users by user ID, or by customer account.
View and extract the event data generated every time a Split feature flag tells your app what treatment to execute.
Benefits to Your Team
- Ship code directly to production as soon as a feature is complete.
- Decouple feature release from code deployment so new features can reach the right users without waiting to be bundled together into one release.
- Expose a new feature to exactly the right group of users.
- Mitigate risk by incrementally rolling out features to your users.
- Instantly make problem code invisible to users without needing to recall a deployment or issuing a patch.