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.
In today's fast-paced digital landscape, users expect seamless, high-quality software experiences without interruptions. As developers, our challenge is introducing new features and updates without causing downtime. The solution? Feature flags. With feature flags, you can safely roll out new features gradually, ensuring your application remains fully operational while the development process continues.
Are you a game developer seeking an efficient way to roll out, manage, and control features in your games? Look no further. With ConfigCat's Unreal Engine SDK, you can seamlessly add feature flags directly into your Unreal Engine projects, allowing you to decouple feature releases from deployments. This not only gives you greater flexibility but also helps streamline your feature development process from start to finish. How does it work in practice? Let's dive in.
As developers, our job often involves regularly releasing new features. But how can we ensure these new features are working properly before safely releasing them to all users? It's simple: by using feature flags!
In a previous post, I covered best practices and tips for using ConfigCat feature flags with Docker. While Docker has advantages for easily sharing and deploying containerized applications, it poses challenges when deploying and managing those containers at scale. This is where Kubernetes comes in. Using feature flags, you can control your Kubernetes deployments and services with a simple click without editing your .yaml config files. Let's take a look together!
In this post, I'll investigate integrating ConfigCat's feature management system with an ASP.NET Core 8 Web API Service and the Options<T> pattern. We'll also leverage the built-in polling mechanism of the ConfigCat client library to refresh feature flags' states during the application's runtime. Let's get started!
In this post, I'm going to be demonstrating how to integrate ConfigCat's feature flags in a React application. I will build a simple, pretty easy-to-understand application that simulates a race between three cars. Let's get started!
Docker is a platform that enables developers to build apps and run them in mini virtual machines called containers. As a result, developers can just focus on writing code without needing to set up or configure an environment for running that code. Docker also allows easy application sharing because its environment is abstracted away from the host machine. This allows the containerized application to run on any host machine Docker is installed on. Developers can extend the functionality of Docker's desktop application with extensions. But the goodness doesn't stop there. You can use feature flags to control smaller feature components of these extensions without rebuilding and updating them.
