LaunchDarkly this week, via a Galaxy update to its feature management platform, added a range of tools to address everything from making it simpler to deliver specific capabilities to end users after an application has been deployed to providing increased observability of workflows.
In addition, the company revealed alliances with GitHub, Bitrise, Snowflake, Twilio and Sentry that make it possible to invoke the feature management platform from within platforms provided by these environments.
Jonathan Nolen, senior vice president of engineering for LaunchDarkly, said the goal is to make it possible to integrate a software-as-a-service (SaaS) platform for managing features both before and after applications are developed with DevOps workflows.
The Galaxy Product Release update specifically adds a Segment Builder tool to make it easier to define what capabilities will be enabled for various groups of users and an Engineering Insights Hub to track velocity and quality metrics.
Other additions include a Release Assistant tool to build pre-defined, repeatable paths for progressive rollouts, a Release Guardian tool to quickly identify and remediate operational regressions, a Migration Assistant tool to help move software from one platform to another and a Mobile Release Optimizations tool.
Finally, LaunchDarkly has added a Funnel Experiments capability to its existing Product Experimentation tool to measure and optimize user behavior.
As more organizations start to deliver different tiers of digital services at varying price points, there is a clear need to be able to restrict access to those digital services. Application development teams have, of course, been employing feature management since the 1970s to isolate the development of various components into a branch that can be worked on and tested without impacting the primary build the application is based on. Feature management, in effect, enables development teams to experiment with adding new capabilities in a way that doesn’t disrupt the application. When a project is completed, that branch is then usually merged into the primary build or can be deployed as a microservice that might be invoked via an application programming interface (API) by other modules with the application or another external application.
At the core of that capability are what are known as feature flags, also known as feature toggles or feature switches, that make it possible to dynamically turn services on or off based on who is accessing them. Rather than being limited to the application development process, those feature flags are now being employed in production environments to enable the continuous delivery of multiple types of digital services to various classes of users of an application. A feature flag management platform enables an organization to keep track of all the flags being employed to keep the overall application environment consistent.
LaunchDarkly is making a case for a SaaS platform that can be used to centrally manage features across multiple workflows as an alternative to employing feature management capabilities embedded with a continuous integration/continuous delivery (CI/CD) platform.
Each organization will need to decide for itself how best to manage features based on how many DevOps platforms they may employ. But it’s clear that feature management is now playing a much larger role in surfacing a wide range of application experiences at a time when organizations are more dependent on software than ever.