We've been working on some updates to make the ConfigCat dashboard easier and more enjoyable for managing your feature flags. Let's take a quick look at these new features.

In software development, engineers and operations teams have a variety of deployment techniques, each with pros and cons. With so many options available, choosing the right release strategy can be challenging, especially when addressing specific problems.

In this blog, we will focus on two deployment strategies, blue/green and ring deployments, which aim to deploy software with minimal risk and disruptions, each using a different approach. These strategies can be applied to a variety of scenarios.

Coming up, we will explore how they work, their ideal use cases, their advantages and disadvantages, and, most importantly, how using a feature flag service like ConfigCat can enhance the flexibility and suitability of both blue/green and ring deployments to meet your specific needs.

Instead of relying on assumptions to decide which variation of a piece of software is better, you can let your users guide the decision through a controlled experiment. A/B testing involves splitting your user base into separate groups, where each group experiences a unique variation of a product or feature. By measuring the performance of each variation, you can determine which one works better.

To conduct such a test, you need a tool that helps you split your users into groups and display the appropriate variation for each group. Feature flags are an ideal tool for this. Let's walk through the process of conducting such an experiment in an Elixir app.

Feature flags have equipped software developers to seamlessly roll out and roll back new features with the click of a button.

Due to their design and architecture, feature flags can be adapted and integrated into many languages and frameworks. They can be used with other technologies to enhance or add decoupled functionalities. Using them when scripting and automating your Unreal Engine editor is no exception to this.

Understanding how users interact with your product's features is essential for delivering optimal user experiences. Twilio Segment and ConfigCat are two great tools that work well together to help you get valuable insights into how users engage with your app. Let's take a look at how it works!

GitOps is a framework that combines the practices of DevOps and Git and applies them to infrastructure management. It is not a tool or platform but a set of standards for managing IT infrastructure using Git. Within this realm, feature flags, like those from ConfigCat, can play a crucial role in streamlining workflows, managing releases, and enabling dynamic configurations.

Let’s dive into how ConfigCat and GitOps work together and why this combination is worth considering for your infrastructure and development processes.

Building and maintaining complex software goes beyond writing code and debugging. To ensure the success of large, complex software projects, developers need clear-cut processes from ideation through to delivery and maintenance. A software development lifecycle (SDLC) offers that. But what exactly is a software development lifecycle? How does it work? And why is it necessary? This article answers these questions and more.

Let's say you've heard about the benefits of using feature flags for gradual feature rollouts, and you're ready to adopt them in your organization. The next step would be deciding whether to "build or buy."

If you choose to develop your feature flagging tool, you'll need to figure out how to make it fetch, evaluate, and manage feature flags. If you want to use a third-party tool, you might have to learn and unlearn different APIs as you search for the right one.

Challenges like these inspired the creation of OpenFeature, a CNCF (Cloud Native Computing Foundation) project that aims to standardize feature flagging.

Feature flags are powerful tools for managing new releases. They let developers toggle features on and off without modifying the underlying code. This method, known as feature flagging, provides flexibility for rolling out updates gradually to specific user groups.

Conducting an A/B test experiment is a popular approach to determining which variation of a particular feature works best for your users. This experiment can shape the success of any product or business. Conducting these tests can be tricky and time-consuming, but with the ideal tools, it doesn't have to be.

If you're a Ruby developer, you're in luck. I'll show you how to perform an A/B test experiment in Ruby using ConfigCat feature flags and how to record the results with Amplitude's data analytics platform. Let's get started!