Latest posts tagged with #OpenFeature on Bluesky
Speaking at #KubeCon Amsterdam!
March 22nd: Building Secure Package Pipelines - sched.co/2EWfG
March 25th: @openfeature.dev Update with the maintainers - sched.co/2EF4j
See you in Amsterdam! 🚀 #KubeCon #OpenSource #OpenFeature #CloudNative #CloudNativeConf
New piece on multi-provider feature flags in .NET with @openfeature.dev Useful if you’re managing flags across different systems or switching providers.
medium.com/@askpt/multi...
#OpenFeature #FeatureFlags #DotNet #csharp
🆕🆓☁️ Feature flagging isn’t just a tool—it’s your edge in release engineering.
Learn safer rollouts, experimentation, and flag management in Feature Flagging with OpenFeature (LFS140).
Enroll free: training.linuxfoundation.org/training/fea...
#DevOps #OpenFeature #FeatureFlagging #SRE #CloudNative
Feature Flagging with #OpenFeature
https://training.linuxfo
#FeatureFlag
🆕🆓☁️ Fast releases impress. Safe, repeatable ones build trust.
Learn Feature Flagging with OpenFeature (LFS140) — a new free course on progressive delivery, experimentation, and safer canary launches.
Enroll now 👉 training.linuxfoundation.org/training/fea...
#OpenFeature #SRE #CloudNative
Great experience speaking at KCD Porto today.
Showed how @openfeature.dev lets us launch features safely with faster releases and smarter targeting.
Thanks to the KDC team for hosting and supporting the community!
#KCDPorto #KCD #CNCF #OpenFeature #dotnet #FeatureFlags
It was a fantastic experience presenting OpenFeature .NET SDK – From A to Z at NDC Porto 2025! Huge thanks to the NDC team for the opportunity and to everyone who joined the session.
#NDCPorto #OpenFeature #dotnet #FeatureFlags @openfeature.dev
I will be speaking about @openfeature.dev at KCD Porto 2025 in Nov 3-4. Excited to share some OpenFeature insights! Feel free to join me!
#KCDPorto2025 #OpenFeature #Kubernetes #CloudNative #dotnet #csharp
community.cncf.io/events/detai...
An image that summarises how many contributions were made by me to this project.
Great to see all the contributions to Cloud Native Computing Foundation (CNCF) for the last 3 years! Happy to see what we achieved at OpenFeature 👏👏👏
#opensource #openfeature #dotnet
Happy to share I’ll be running a hands-on workshop at NDC Porto:
“OpenFeature .NET SDK – From A to Z”
Learn how to bring safe, modern feature management to your .NET apps with OpenFeature.
Details: ndcporto.com/workshops/openfeature-net-sdk-from-a-to-z/794f1fc20166
#dotnet #openfeature #featureflags
Bob Walker presents 'How we progressively deliver changes to 1000s of customers with Canary Deployments and Feature Flags' July 24th at Nebraska.Code().
nebraskacode.amegala.com
#Kubernetes #canarydeployments #openfeature #DeliveryPipeline #featureflags #softwareengineering #Nebraska
Giving my "Fun with Flags" talk at Java Vienna tonight! 🎤
How we're solving common feature flagging headaches with @openfeature.dev.
Come say hi!
🔗 www.meetup.com/java-vienna/...
#Java #OpenFeature #FeatureFlags
Explore how @openfeature.dev easily integrates with #fsharp in my most recent blog post: medium.com/@askpt/openf... #OpenFeature #dotnet #fsharp
Discover the power of @openfeature.dev in .NET! Learn how to integrate feature flagging into your ASP.NET Core apps with this insightful intro: blog.kylejulian.dev/posts/open-f... #OpenFeature #dotnet
OpenFeature team members
GitHub cool badge
Presentation about OpenFeature
KubeCon main entrance
Back from an incredible week at #KubeCon London! I loved connecting with fellow tech enthusiasts. Special shoutout to our @openfeature.dev team for sharing insights on feature flagging. Our project discussions were enlightening! Great to meet the folks @github.com. #CloudNative #OpenFeature
What’s new in @openfeature.dev? Today these updates were announced at #KubeCon + #CloudNativeCon and more!
Which update are you most excited about?
#dynatraceatkubecon #openfeature
Giulia from the DevRel team at Dynatrace will take you on a trip to #KubeCon + #CloudNativeCon London 2025.
Stay tuned for updates on what's happening in the cloud-native world, particularly with #OpenTelemetry and #OpenFeature.
@giuliadp.bsky.social
Title slide for the presentation, Beyond Boolean, which features a large mountain with a tiny orange feature flag on top
I'm speaking today at #KubeCon London, as part of the #OpenFeature summit. Come hear my talk, Beyond Boolean, where I discuss some of the challenges teams face when flagging at scale and how we help you solve those problems at @growthbook.io
*8d -> #KubeCon & a bit of #OpenFeature a day #16*
#OFREP is short for OpenFeature #Remote #Evaluation #Protocol. It is a protocol specification for the #communication between #providers and feature flag management systems that support it.
Find it on github.com/open-feature/protocol
*10d -> #KubeCon & a bit of #OpenFeature a day #15*
With the specification of the #TrackingAPI, we can tie application #metrics & the feature flag system together; without requiring a vendor to support flag #analytics or having 2 separate systems; we can send all data to the same analytics backend!
*12d -> #KubeCon & a bit of #OpenFeature a day #14*
TIL: using the #OpenTelemetry #protocol ( #OTLP ) applications can be instrumented to send #telemetry data to analytics backends. This even works when running the app #locally!
Pro tip: set the env var 'OTEL_LOG_LEVEL=debug' for development
*17d -> #KubeCon & a bit of #OpenFeature a day #13*
The OF #project consists of >40 #repositories. Most essential to the standard are:
/spec: contains the standardization
/*-sdk repos: language-specific #SDK implementations of the spec
/*-sdk-contrib: lang-specific provider & hook #implementations
The table in the image shows the mapping between OpenTelemetry feature flag log record conventions and OpenFeature evaluation details fields. Eg. log record attribute 'feature_flag.key' can be mapped to 'flag key'
*22d -> #KubeCon & a bit of #OpenFeature a day #12*
#EvaluationDetails are a flag evaluation's returned data structure. It contains data like the #flagKey, #errorCode, #variant, #reason & #metadata, such as #contextId or #flagSetId. These can be mapped to #OpenTelemetry #log #record conventions.
In the TypeScript code snippet, one can see how an event handler can be added to the OpenFeature client. It shows 2 examples for event type ready and configuration changed.
*25d -> #KubeCon & a bit of #OpenFeature a day #11*
#Events are state changes of the #provider: ready, configuration changed, error, stale
#Event #handlers can be implemented to react to those. Eg. maybe we want to wait until the provider is 'ready' before evaluating feature flags for rendering UI.
🆕 New to OpenFeature? Here’s a great video from @betterstack.com 📚 that gives a full overview: www.youtube.com/watch?v=ZJzQ... #OpenFeature #OpenStandards #FeatureFlagging #ABTesting
The code snippet shows how the OpenFeature client's track function is called passing a tracking event name and TrackingEventDetails, which consist of a numeric value here. In the example, the 'clicked-checkout' event is tracked with a value of 99.77. For server-side applications, the evaluation context parameter can be optionally passed to analyze tracking events in the context of the current user session.
*27d -> #KubeCon & a bit of #OpenFeature a day #10*
Looking at actual #code examples makes it obvious what #tracking calls are used for. Calling the #track function via the #OF #client and passing #TrackingEventDetails a numeric value and other optional data can be sent to the backend:
Join us tomorrow for #YouChoose
This time we’re exploring miscellaneous tools related to IDPs - fun!
We’ll compare #Dapr, #KusionStack, & #OpenFeature with 5-minute presentations from experts, followed by Q&A. Then VOTE on which tool we implement in our demo!
Hit 'Notify me'
youtu.be/e2aHoiKH5Jk
This java code snippet shows how a provider can be implemented to support tracking. It implements the Tracking interface by implementing a track function that returns void. As parameters an event name, an evaluation context and tracking event details can be passed.
*29d -> #KubeCon & a bit of #OpenFeature a day #9*
To support tracking the OpenFeature #provider needs to implement the #Tracking interface, which contains a single function called track. This function performs #side-effects to record the tracking #event (e.g. store a specific metric).
The sequence diagram shows the function calls that are necessary to implement tracking. A tracking hook sends data about flag evaluations coming from the Evaluation API to the Analytics Platform. A separate track call from the Evaluation API to the Analytics Platform stores data about the user session.
*32d -> #KubeCon & a bit of #OpenFeature a day #8*
How does #tracking work?
Calling a #track function stores certain #metrics for a user session (e.g. total purchase amount). #Hooks can be used to store info about #flag #evaluations. Combined, one can see, e.g., how a new feature impacts purchases.
*33 days until #KubeCon & a bit of #OpenFeature a day Nr. 7*
#Experimentation is the term for testing the #impact of a new feature. Certain #metrics of the new feature can be #tracked to, e.g., check if users even like to use the new feature. #Tracking enables product decisions based on #data.
