Skip to main content

· 2 min read
Gergely Sinka

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.

Requests per month Total config.json downloads by 28 Dec, 2020

· 6 min read
Jan Sipos

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.

Graphs and charts representing user segmentation

· 5 min read
Petrina Georgousi

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.

Cameras

· 7 min read
Jan Sipos

Let's say you've just built a new feature, but it's not ready for a full release just yet. So, you decide to test it with a small group of people.

Image with sticky notes

You can go about it in two ways - deterministic or random. The first way lets you specify people by name, email, company or any other attribute you know about them. The latter uses fancy math and probability to randomly assign users into groups. Let's see how you'd accomplish both using ConfigCat.

· 4 min read
Endre Toth

When I implement a new feature to my application, I would like to manage it after the release (enable, target, tune and obviously in urgent cases roll it back). The feature/release toggles design pattern can solve my issue, but how can I answer the business needs? For example:

  • turn on the feature on Sunday at 12 PM
  • increase the discount value of the promotion every workday
  • enable the feature only on weekends or on weekdays

· 5 min read
Csilla Kisfaludi

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 Global CDN map

· 3 min read
Zoltan David

When it comes to feature flags, teams with 5-20 engineers face similar challenges to teams with hundreds of developers. What you never want is one engineer flipping a feature toggle to unintentionally affect the work of another engineer.

This is a conceptual problem with feature flags. It doesn't matter if you are using an open-source feature flag tool, or a feature flag service. Let's see best practices ConfigCat recommends.

· 6 min read
Lajos Szőke

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.