This talk introduces several strategies how to roll out changes premptively without immediate activation. This can be used to make features available early for pilot customers or only with a special license. Similarly features can rolled back quickly, in case something goes wrong. Like many patterns this comes at the price of higher complexity.
The condition service spec allows to bind to such feature flags without coupling your code to a specific feature flag tooling.
We also discuss how to phase out the feature flags to make sure the code stays lean.
A small demo shows how to conditionally switch features from a central console even at runtime without redploying the application to the cloud.