In the days of XCopy deployments, configuration was simple. Put stuff on the server and then tweak the configuration. But with more sophisticated deployment pipelines, configuration becomes a much more time-consuming problem. Each environment has its own database, connecting strings, and more. Plus, in some of those environments, you might mock external dependencies, while in others you want to use parallel sandbox environments. Even with automation, it’s easy to lose track.
Feature Flags in Higher Deployment Environments
Nowhere is this complexity felt more acutely than in areas where your application selectively guarded by feature flags. If you’re toggling database access, external dependencies, etc, that means you’re managing this not just in development and production, but in every environment in between. If you’ve implemented manual feature flagging, you’re going to have a serious headache on your hand.
With a feature flag management system in place, however, you can make your life much easier. With Rollout, you can manage this out of the box. For each of your feature flags, deploy it differently in every one of your environments, allowing you to test it according to your needs. You can even implement feature rollout migration between your environments, helping you make a smoother transition.
As the field of DevOps evolves, you’re only going to need more environments, automation, and flexibility. Get out in front of that need by using a feature flag management system to manage your features across all environments.