Feature flags help teams release features safely and quickly, but if left unmanaged, they can become stale and accumulate technical debt. To keep your codebase clean, you can use the Zombie Flags page, the Zombie Flags Report, and the Zombie Flags API. Let’s take a closer look at each of them.
Are you considering a switch from LaunchDarkly? Whether you're looking for more flexibility, cost-efficiency, or just a smoother developer experience, ConfigCat offers a refreshingly straightforward alternative. With a built-in import tool and transparent SDKs, moving your feature flags over is quicker than you might think. In this guide, we’ll walk you through the migration process - without breaking a sweat (or your codebase).
Does it matter whether you evaluate feature flags on the backend or the frontend? The answer is yes. As you might have guessed, the frontend and backend are distinct components of software architecture—and the factors we consider when working with them, such as security and control, apply to feature flags as well.
In this article, we'll explore the pros and cons of backend and frontend feature flags and solutions to challenges you may face while working with them.
Before the open source movement, software programs were 'closed source,' meaning only software developers employed by the company could access and modify them. Outsiders were kept out through non-disclosure agreements and licenses. This exclusivity motivated the creation of the open-source movement, aiming to preserve the freedom to modify and distribute software through publicly accessible code. Today, many commercial companies actively participate in the open-source ecosystem, maintaining software that is open to the public for access and contributions. One such company supporting this effort is ConfigCat.
When it comes to shipping features fast and confidently, feature flags are your secret weapon. They let you roll out updates safely, test in production, and avoid deployment risks. But here's the big question: should you build your own feature flag system, or choose a ready-made solution like ConfigCat?
At ConfigCat, we've seen firsthand how feature flags help teams ship faster with less risk and build more resilient, user-friendly applications. We want more people to experience these benefits, so we've decided to officially support OpenFeature.
Our OpenFeature providers were previously developed and maintained by open-source contributors. Moving forward, we've opted to develop and maintain some providers in-house, while continuing to collaborate with open-source contributors for others.
In the upcoming sections, we'll explore how to integrate OpenFeature into a Python application that currently uses the ConfigCat Python SDK.
As the gaming industry continues to evolve, driven by technological advancement and an ever-growing demand for more immersive, engaging experiences, players no longer settle for static and predictable game worlds—they crave dynamic environments that respond and adapt to their actions in real-time.
This shift toward adaptive gaming revolutionizes development techniques, enabling developers to craft personalized gameplay as unique as the player behind the controller. At the heart of this transformation lies a powerful tool: feature flags.
Hey, Rustaceans! We developed the Rust SDK in response to a feature request from one of our customers, OneSignal. When we heard about their needs, we rolled up our sleeves and released the Rust SDK two months later. With it, you can manage feature flags like a pro—whether starting a new project or optimizing an existing app. It allows you to toggle features on and off without redeploying your code. That's right—no more redeploys every time your boss changes their mind about a button color!
With ConfigCat's feature flags, you can gradually roll out new features, rigorously test them (in a controlled environment, of course), and make changes on the fly—all directly from your dashboard! Let's dive into why this is a game-changer for your development workflow.
We've been working on some updates to make the ConfigCat dashboard easier and more enjoyable for managing your feature flags. Let's take a quick look at these new features.
In software development, engineers and operations teams have a variety of deployment techniques, each with pros and cons. With so many options available, choosing the right release strategy can be challenging, especially when addressing specific problems.
In this blog, we will focus on two deployment strategies, blue/green and ring deployments, which aim to deploy software with minimal risk and disruptions, each using a different approach. These strategies can be applied to a variety of scenarios.
Coming up, we will explore how they work, their ideal use cases, their advantages and disadvantages, and, most importantly, how using a feature flag service like ConfigCat can enhance the flexibility and suitability of both blue/green and ring deployments to meet your specific needs.
