At the beginning of this year, Andrew Reeman from Control Point was kind enough to join our conversation about what we actually do differently at ConfigCat, or at least interesting enough so that it only makes sense for our clients to stick with us and for those who didn’t try our approach and products, to do so.
When growing any product or service, it’s to constantly gather feedback from your user base. And I mean constantly, else you risk losing focus from your real clients’ needs and priorities.
To drive this point home, I figured that the best course of action was to collect some valuable insight from a third-party. Joseph Harris, who works at Eucalyptus was kind enough to take the time and offer just that.
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.