13 posts tagged with "openfeature"

AI coding assistants have become a regular part of the developer workflow — writing boilerplate, suggesting configurations, explaining APIs. But when it comes to feature flags, generic AI often gets the details wrong: incorrect flag schema, outdated OpenFeature SDK patterns, or relay proxy configuration that doesn't quite match what GO Feature Flag expects.

Community members have built tools that fix this — injecting domain knowledge directly into your AI assistant so it generates accurate, idiomatic code from the start.

Thomas Poignant, creator of GO Feature Flag, has been elected to the OpenFeature Governance Committee for the 2026-2028 term. This is a milestone to be genuinely proud of — and one that feels like a natural continuation of the work done at the intersection of GO Feature Flag and the OpenFeature ecosystem.

KubeCon + CloudNativeCon Europe 2026 in Amsterdam is behind us, and what a week it was. For GO Feature Flag, it was both an opportunity to represent the project on a big stage and to connect directly with the community in person.

We are excited to introduce in-process evaluation for the GO Feature Flag OpenFeature server providers: Go, Java, .NET, Python, JavaScript, and TypeScript.

This capability is designed to improve evaluation performance and drastically reduce network traffic between your applications and the relay-proxy.

What changes with in-process evaluation?​

Previously, when you used the OpenFeature providers we ship, evaluation used remote evaluation: each flag evaluation triggered a network call to the relay-proxy.

That model fits many setups, but it is not always the most performant or resilient way to evaluate feature flags on hot paths.

That is why we are launching in-process evaluation mode for our most widely used providers.

We're excited to share that Thomas Poignant, creator of GO Feature Flag, presented an insightful talk at PlatformCon 2025 about decoupling deployments from feature releases using OpenFeature.

Talk: "Decouple Deployments and Releases with OpenFeature"​

In this presentation, Thomas explores how traditional deployment strategies often directly couple feature releases with code deployments, increasing risks and slowing time-to-market. He demonstrates how OpenFeature, a vendor-agnostic API for feature flagging, enables developers to separate feature releases from code deployments, providing precise control over feature visibility and experimentation.

This blog post dives into a new functionality introduced in the GO Feature Flag provider for OpenFeature: exporter metadata. We'll explore how it works and how you can leverage it to enrich your evaluation events with valuable static information.

What is Exporter Metadata?​

Exporter metadata is an object you can configure when initializing your GO Feature Flag provider for OpenFeature.

It allows you to specify a set of static information that you want to consistently include with all your evaluation events. A good example of information you might include in exporter metadata is the environment in which your application is running, the version of the application or anything that helps you when you analyze your evaluation data.

This data is then forwarded to the exporter and incorporated into your feature events as a new field called metadata.

Until Today the java provider, used the guava cache to store the flags and the segments. Using the guava cache is now discouraged by the guava team.

In order to follow the guidance of the guava team, we have decided to migrate the internal cache of the Java provider from guava to caffeine.

This may create a breaking change for you if you were using a custom cache configuration with the guava cache in your provider.
Because of this, the cache configuration on GoFeatureFlagProviderOptions that used Guava's CacheBuilder is now handled by Caffeine.

We're excited to announce significant improvements to the integration between GO Feature Flag and OpenFeature.

To better serve our users' diverse needs, we've decided to split the previous Go provider into two distinct providers:

• go-feature-flag: For use with the GO Feature Flag relay proxy.
• go-feature-flag-in-process: For direct integration of GO Feature Flag into your application.

Thomas recently delivered a presentation on Feature Flagging in the Software Development Lifecycle (SDLC) for OpenFeature. Given the presentation's public availability, we are pleased to share the slides with you.

Effective management of the feature flag lifecycle is crucial for maximizing the value of feature flags within an organization.

This presentation is covering the following key areas:

• Feature flag lifecycle: Understanding the complete journey of a feature flag.
• Roles and responsibilities: Identifying who owns each phase of the lifecycle.
• Feature flag naming conventions: Best practices for clear and consistent flag identification.
• Preventing flag debt: Strategies for avoiding the accumulation of unused or obsolete flags.
• Involving project managers: The importance of project management collaboration in feature flag initiatives.

By understanding these concepts, you can optimize your feature flagging strategy and drive business success.

We're thrilled to announce a major milestone for GO Feature Flag: full compatibility with mobile applications. That's right, you can now leverage the power of feature flags to optimize your iOS, Android, and React Native apps with unparalleled ease and flexibility.