Microservices Architecture is a revolutionary approach to software development that empowers applications to scale and evolve with unparalleled flexibility. But: How do feature flags help in this dynamic landscape of microservices?
At Kantan, we're changing the lives of tradespeople by giving them the tools to excel in a competitive marketplace. Our product is a React Native app that helps them serve customers, manage operations and grow their business. We have thousands of tradespeople managing hundreds of thousands of jobs on our platform. And we are just getting started.
To enable us to grow and scale on the journey to become the number one application for tradespeople in the UK, we need to move quickly, pushing our product and features to market faster than our competitors whilst maintaining quality and ensuring we have complete control over our production environment.
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.
When growing any product or service, it’s to constantly gather feedback from your user base. And I mean constantly, else you risk losing focus from your real clients’ needs and priorities.
To drive this point home, I figured that the best course of action was to collect some valuable insight from a third-party. Joseph Harris, who works at Eucalyptus was kind enough to take the time and offer just that.