Book Image

Feature Management with LaunchDarkly

By : Michael Gillett
Book Image

Feature Management with LaunchDarkly

By: Michael Gillett

Overview of this book

Over the past few years, DevOps has become the de facto approach for designing, building, and delivering software. Feature management is now extending the DevOps methodology to allow applications to change on demand and run experiments to validate the success of new features. If you want to make feature management happen, LaunchDarkly is the tool for you. This book explains how feature management is key to building modern software systems. Starting with the basics of LaunchDarkly and configuring simple feature flags to turn features on and off, you'll learn how simple functionality can be applied in more powerful ways with percentage-based rollouts, experimentation, and switches. You'll see how feature management can change the way teams work and how large projects, including migrations, are planned. Finally, you'll discover various uses of every part of the tool to gain mastery of LaunchDarkly. This includes tips and tricks for experimentation, identifying groups and segments of users, and investigating and debugging issues with specific users and feature flag evaluations. By the end of the book, you'll have gained a comprehensive understanding of LaunchDarkly, along with knowledge of the adoption of trunk-based development workflows and methods, multi-variant testing, and managing infrastructure changes and migrations.
Table of Contents (18 chapters)
1
Section 1: The Basics
5
Section 2:Getting the Most out of Feature Management
11
Section 3: Mastering LaunchDarkly

Understanding temporary feature flags

Now that we have looked at feature management and learned how to implement a feature flag, I am going to discuss the use of temporary feature flags. As the name suggests, the point of these feature flags is that they are disposable with a plan to remove them from the code base at some point. Often, this is the best use case for feature management, but there are some scenarios that we will look at later where you will require a permanent feature flag.

The reason feature flags can often be considered short-lived is that flags can be effectively used to deliver new components safely to production. Once a feature is delivered to production, a flag can be used to make the component available to some or all customers. Once the feature has been released for all users, the flag will have served its purpose.

Feature management is often used to better understand how a feature works in production, to become confident with its implementation, and to...