Welcome to CloudBees Feature Management! This page is the best place to start learning the basics of CloudBees Feature Management, what problems it solves, and how it compares to other solutions.
CloudBees Feature Management is a feature management platform that enables team to progressively toggle features on and off for certain segments of users. Once users are targeted by certain attributes, CloudBees Feature Management makes it simple to roll out different features to them - managing who is seeing what when.
Feature flags were made popular by companies like Netflix, FaceBook, and Amazon and help them deploy hundreds of times a day, test in production, experiment with their products, and more.
CloudBees Feature Management is built around the following core features:
Feature flags
Feature flags are little snippets of code that go around certain blocks of feature code, that can remotely enable that feature on or off. We say remotely, because the feature toggle can be turned on or off for applications even while they are in Production!
if(paymentFlag.isEnabled()){
//New Feature Code
}
else{
//Current Code
}They can be implemented on the client side or server side and help teams achieve Continuous Delivery with less risk.
Target Groups
Target Groups are segments of users that flags are displayed to. Target Groups can be made up of segments with attributes and commonalities like geo region, browser, email, or custom attributes like Plan Type or Account ID.
Progressive releases
Once feature flags have been created and a Target Group selected, it is time to "roll" our feature out. We can do this a number of ways, including by percentages, time, etc. We call this Progressive Delivery.
Configuration as Code
Configuration as Code (CAC) allows the entire configuration of CloudBees Feature Management to be stored as source code. It integrates the CloudBees Feature Management UI with your existing environment. This approach brings a lot of benefits.