In this post, we’ll look at how we can easily implement a canary release of a feature in 7 steps using ConfigCat’s feature flagging service through its provided dashboard.
This step-by-step guide will showcase how we can release a new feature incrementally, by first exposing it to low-risk user groups (e.g. team members and possibly friends), and then gradually releasing it to a larger audience - using ConfigCat, a feature flag service to implement everything.
Let's take a look at how practical a feature flag can be in a Phaser.io application. Phaser is one of the most popular browser game libraries and with its help, I'll build a simple game that replicates the experience of being in a music studio. Let's get started!
Feature flags have greatly simplified the process of continuously testing and integrating new features into our applications. They ensure confidence even in production environments, eliminating deployment risks such as downtimes or bugs that could adversely affect the entire user base.
Let's play with a hypothetical scenario where you've built a Kotlin-based mobile application, and you'd like to customize the overall user experience based on specified criteria. You've got a perfect idea, but then this question pops up everywhere: Now what? Folks, allow me to introduce you to the concept of feature flags in Kotlin.
Building a modern application often involves building it as a microservice, which provides developers with more flexibility and agility in terms of deployment options. However, deployment can either be a joy or a nightmare, depending on the strategy used, whether it's deploying microservices, testing new features, updating a business logic, or releasing a new version entirely? With every code change pushed, comes the risk of potential failures, which could be as a result of bad code quality or unexpected bugs, and this can potentially disrupt the user's experience.
Hence, picking an efficient deployment strategy is key to mitigating these deployment risks and not having to constantly disrupt your user’s experience by going into downtimes or completely having to go offline whenever there is something to be deployed.
We at ConfigCat are thrilled and proud to announce that ConfigCat was awarded the prestigious “High Performer” award by G2 in their winter 2022 report for Configuration Management Software. These awards are given based on customers' feedback on products or services that they use, which makes them especially prestigious.
In the context of SaaS applications, having a tool that allows you to control different features and flag certain users is critical, given the uniqueness of their needs and the instability of new releases.
This is where the ConfigCat Elixir SDK's tale begins. This is the simplified narrative of a great open-source SDK, driven by highly-professional folks from three different companies, as told by one of its creators.
A remote code execution flaw was recently discovered in log4j. The vulnerability is fixed in log4j 2.15.0.
Log4j is a popular Java logging library. It is used by many popular Java applications. We have double-checked our systems and SDKs to be sure that they are not affected by this vulnerability.
Bugfender is a remote log aggregator that allows front-end and mobile developers to view their entire crash and issue records from any location. It works on iOS, Android and web applications and provides crucial information at all three development stages (development, testing and production).
By harnessing Bugfender, ConfigCat users can provide even more targeted support by identifying bugs in their individual features as well as overarching trends.
Coming from LaunchDarkly? This post will show you a simple & straight forward way to migrate your feature flags from LaunchDarkly to ConfigCat
