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.

ConfigCat is NOT affected.

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.

In this article, I’m going to be demonstrating how to integrate ConfigCat's Feature Flag service in React. I will build a simple, pretty easy-to-understand application that simulates a race between three cars. Let’s get started!

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

Before we know what the Non-Fungible Token (NFT) is, we need to know what’s the technology behind it, which’s Blockchain.

When we say Blockchain, people tend to start thinking about Bitcoin, Etherum, Doge, etc… These are cryptocurrencies. Blockchain is the underlying technology beneath that. So basically Blockchain Technology can exist without cryptocurrencies, but cryptocurrencies can’t exist without Blockchain and the same principle applies to NFTs.

Blockchain Technology is a big decentralized system that lets you record data in ways that make it hard or impossible to have changes on it or to hack it. Think of it as a series of blocks that are tied together like a chain. Each block has data, mostly transactions, and keep in mind that blockchain is transparent by nature, so you’ll be able to track the entire transaction history made using Blockchain.

In this post I investigate integrating ConfigCat's feature management with an ASP.NET Core 6 web API service and the Options<T> pattern. I will also focus on using the AutoPolling mechanism built into the ConfigCat client library, to refresh feature flags' state during application runtime.

Between 28th and 30th September, our customers experienced long response times, timeouts, and failing responses from the ConfigCat CDN. Since this was a significant disruption in the ConfigCat service, we want to be upfront about it and share all the information about what happened, what we've done, and what changes we will implement.