There are many reasons why you don't want to keep unnecessary feature flags around you.
One way to make sure you do not forget about your old flags is by subscribing to the Stale Feature Flags Report.
Thanks to the latest CI/CD tools and services, software companies can now deliver multiple releases in a week. Over the release process, it's expected that DevOps professionals keep their eyes on the monitoring dashboard and roll-back the deployment on the first suspicion. Since the use of feature flags gets more and more traction, it seems like a good idea to connect those releases and the monitoring tools.
We tend to move quickly from release to release and forget to honor the magnitude of our achievements during the year. Let this post be here as a milestone for the ConfigCat team to stop for a second, look back, and celebrate the preposterous performance we did.
Total config JSON downloads by 28 Dec, 2020
Separating your customers into distinct segments will help your product in all sorts of ways. It can help you track the usage of your app in a more meaningful and granular way. It can also reveal how specifically different segments behave differently, which will help you prioritize future feature development as well as focus your marketing efforts.
Last July, the Privacy Shield, which had been so useful for companies doing business on both sides of the Atlantic, became ineffective. It took us all by surprise, since it was quite a new program (only 4 years old) building the framework for exchange of information and data between the United States (US) and the European Union (EU) and it had eased a lot the business between the two markets.
When we designed ConfigCat, our main purpose was to create an architecture that is scalable and resilient to short interruptions, so you don't have to worry about latency, service outages, and unwanted glitches in the system.
ConfigCat's validation phase was a success in our eyes, so we had to step ahead. Above making a great product with great features we had to provide a really stable and reliable system.
In the next few articles I would like to introduce the core infrastructure of ConfigCat, how it has evolved over time and what challenges we faced through its validation phases.
Ever since we heard about Zapier we have been ecstatic by the possibilities this could bring to our platform. Zapier is an integration platform that allows you to easily connect multiple platforms by taking inputs from one service and outputting them to another service. While software integration is common, some integration may not be appropriate for your technology stack, or native integration may not yet be supported. This is where Zapier can step in and save the day.
A updated version of this blog post is available here.
Nowadays, thanks to modern continuous delivery tools, many software development processes make it easy to deliver multiple releases per week. It is often common for several scheduled releases per week to be released. The usual practice is that during the release process, DevOps guys keep their eyes on the monitoring dashboard, and if they find any anomalies, they roll back the version.
But what happens if someone changes a feature flag's value (release toggles) in the production environment?
Release Toggles allow incomplete and un-tested code paths to be shipped to production as latent code which may never be turned on. https://martinfowler.com/articles/feature-toggles.html
DevOps are notified that a certain threshold has been reached for the production environment and that when they open a related metric they see something similar:
