Skip to content
The guide to decoupling feature rollout from code deployment for feature flag-driven development. Feature flags give a software organization the power to reduce risk, iterate quicker, and get more control.
Branch: master
Clone or download
Latest commit 3cc8f9f Oct 1, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
1 - Introduction.md
2 - Uses.md Tidy up pages 2 and 3 Jul 31, 2018
3 - Getting Started.md Tidy up pages 2 and 3 Jul 31, 2018
4 - Cleaning Up.md Update 4 - Cleaning Up.md Mar 29, 2017
5 - Best Practices.md Trivial typofix Mar 6, 2018
6 - Flags vs Branching.md Fixed broken images Jun 5, 2018
7 - Blue-Green Deployments.md Fixed broken images Jun 5, 2018
8 - Database Migrations.md Update 8 - Database Migrations.md Jun 6, 2018
9 - Implementation.md Some final considerations before you implement. Dec 4, 2016
README.md Update README.md Nov 20, 2017

README.md

Table of Contents

  1. Introduction
  2. Uses
  3. Getting Started
  4. Cleaning Up
  5. Best Practices
  6. Flags vs Branching
  7. Blue-Green Deployments
  8. Database Migrations
  9. Implementation

Welcome to the new home of our Feature Flagging Guide.

LaunchDarkly serves 4 billion feature flags daily to help software teams build better software, faster. LaunchDarkly gives you the power to separate feature rollout from code deployment and manage feature flags at scale. Ultimately, you can deliver faster, more personalized software with less risk.

About LaunchDarkly

LaunchDarkly is a continuous delivery platform that provides feature flags as a service and allows developers to iterate quickly and safely. We allow you to easily flag your features and manage them from the LaunchDarkly dashboard. With LaunchDarkly, you can:

  • Roll out a new feature to a subset of your users (like a group of users who opt-in to a beta tester group), gathering feedback and bug reports from real-world use cases.
  • Gradually roll out a feature to an increasing percentage of users, and track the effect that the feature has on key metrics (for instance, how likely is a user to complete a purchase if they have feature A versus feature B?).
  • Turn off a feature that you realize is causing performance problems in production, without needing to re-deploy, or even restart the application with a changed configuration file.
  • Grant access to certain features based on user attributes, like payment plan (eg: users on the ‘gold’ plan get access to more features than users in the ‘silver’ plan). Disable parts of your application to facilitate maintenance, without taking everything offline.

LaunchDarkly provides feature flag SDKs for

Many of the specific uses for LaunchDarkly’s features are covered within the uses section of our guide, although we recommend you start with the first chapter for a comprehensive overview. For other questions, technical or otherwise, feel free to visit our site’s FAQ or our support page!

Integrations

LaunchDarkly has numerous software integrations that are designed to make your experience smoother when using feature flags in combination with other products. These include:

Community

Our community is open to anyone with interest in feature flagging or dark launching software! Feel free to head to any of the following links for more information, and a warm welcome into the world of dark launching.

Known issues

For all known issues, visit the LaunchDarkly support page for help.

Contributions

Our guide and SDKs are all open source, and we encourage pull-requests and other contributions from the community. If you have a suggestion or correction for our guide feel free to commit a pull request on this repo and it will be reviewed.

When contributing please ensure that you do the following:

  1. Read through our Contributor’s Guide before submitting any SDK pull requests.
  2. Create a new branch for each different change.
You can’t perform that action at this time.