Source: thenewstack.io
Building a Standard Interface for Feature Flags with Node.js
To have more predictable releases, it’s essential to create a standard process for how flags are used. At LogDNA, feature flags were part of our software development life cycle (SDLC), but weren’t organized in a standard way, which led to confusion across the organization.
There are cases where we want to toggle a feature only for IBM accounts or only for LogDNA accounts.
We wanted it to be able to read flags from LaunchDarkly, enforce some validation and format the user data before it’s sent to LaunchDarkly to request a feature flag.
For the LogDNA engineering team, adopting LaunchDarkly was the first step in rolling out a robust feature flagging process.
There are cases where we want to toggle a feature only for IBM accounts or only for LogDNA accounts.
We wanted it to be able to read flags from LaunchDarkly, enforce some validation and format the user data before it’s sent to LaunchDarkly to request a feature flag.
For the LogDNA engineering team, adopting LaunchDarkly was the first step in rolling out a robust feature flagging process.
Related Articles
Community Partners
DevOps Careers