Zoltan David

Clients with global customer bases often hesitate to use feature flags for specific use cases due to concerns regarding possible latency and slow response time. Feature flags let you launch new features and change your software configuration without (re)deploying code.

That's why fast response time is of great importance at ConfigCat. For context, ConfigCat is a developer-centric feature flag service with unlimited team size, awesome support, and a reasonable price tag.

To that end, ConfigCat provides data centers at numerous global locations to ensure high availability and fast response time all around the globe. These data centers are all equipped with multiple CDN nodes to guarantee proper redundancy and multiple layers of load balancing based on geolocation to achieve speed, throughput, reliability, and compliance. Thanks to a previous DDoS incident, ConfigCat also got the chance to test its infrastructure in real life and made preemptive security improvements.

By now, you’re probably well-acquainted with the suite of useful feature flag tools offered by ConfigCat. In case you aren't, ConfigCat is a developer-centric feature flag service with unlimited team size, awesome support, and a reasonable price tag. Let's play it safe and discuss 3 cool things that ConfigCat allows you to do – which we bet you didn’t know about! I’ll cover:

• Purchasing a ConfigCat subscription for someone else
• Enabling Two-Factor Authentication (2FA) in ConfigCat
• Getting a free feature flag pack for students

Let’s get started!

If you’ve been reading about feature flags then I’m sure you’re convinced of the power and value they provide. Since development is mostly a team effort, you may be wondering how to manage a feature flag within a team, regardless of size, so one developer’s work doesn’t affect another’s. Well, in this article, we discuss exactly this issue and offer two solutions, depending on the size of your team.

Picture this: You’ve added a new feature to your software, linked it to a feature flag, and deployed it to production. Now, you’d like to enable this feature for a subset of your users to get their feedback before you take the leap and roll it out to everyone.

But who gets to see this new feature first? How do you choose the first user segment? How do you use feature flag rules to target them?

Good to know: Feature flags let you launch new features and change your software configuration without (re)deploying code.

Let’s look at some typical real-world examples of how you can do canary releases using ConfigCat.

How to not forget important flags​

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.

TL;DR​

If you're a software reseller you are allowed to buy a ConfigCat subscription for your client. You are allowed to resell one subscription to one client only. Of course, you are allowed to resell more subscriptions to the same client.

Here is how to do it.

Feature flag services are getting popular, but...​

As feature flags are getting popular, an ever-growing number of developers are facing the challenges associated with them.

No matter if you implement your own feature flag library, or choose a hosted feature flag service like ConfigCat, chances are high you want to use your feature flags in your frontend and in your backend services as well.

If your feature flags can be toggled on a central feature flag dashboard, such as

"Thank you guys, you rock."​

We love to get emails like the one above. And sometimes we do. 😃 Actually, more often than I've ever dared to imagine.

Part of the reason our users love us (well, when they do) are those million little tweaks we do to our feature flag service on a daily basis.

Normally we don't share those little tweaks and updates