OpenFeature – a vendor-agnostic, community-driven API for feature flagging • Hacker News Board

OpenFeature – a vendor-agnostic, community-driven API for feature flagging

#1

Post by gjvc » Fri, Oct 25, 2024, 1:26 AM UTC

OpenFeature – a vendor-agnostic, community-driven API for feature flagging
github.com

Re: OpenFeature – a vendor-agnostic, community-driven API for feature flagging

#2

Post by cmckn » Fri, Oct 25, 2024, 3:21 AM UTC

Looks like an interesting project. Really cute logo. :)

How much does the flagd sidecar cost? Seems like that could be a lot of overhead for this one bit of functionality.

Re: OpenFeature – a vendor-agnostic, community-driven API for feature flagging

#3

Post by sgammon » Fri, Oct 25, 2024, 4:30 AM UTC

java version embeds lombok symbols lol

Re: OpenFeature – a vendor-agnostic, community-driven API for feature flagging

#4

Post by abrahms » Fri, Oct 25, 2024, 5:16 AM UTC

sgammon wrote: post #3

java version embeds lombok symbols lol

Forgive my ignorance, but what should it be doing instead?

Re: OpenFeature – a vendor-agnostic, community-driven API for feature flagging

#5

Post by sabedevops » Fri, Oct 25, 2024, 5:30 AM UTC

Where is the tldr? Anyone familiar…what does this do and why do we care about it being standards based?

Re: OpenFeature – a vendor-agnostic, community-driven API for feature flagging

#6

Post by MeteorMarc » Fri, Oct 25, 2024, 5:44 AM UTC

Martin Fowler about feature flags: https://martinfowler.com/articles/feature-toggles.html

Re: OpenFeature – a vendor-agnostic, community-driven API for feature flagging

#7

Post by fire_lake » Fri, Oct 25, 2024, 5:47 AM UTC

I don’t get it. Why is this needed above and beyond the standard ways of configuring deployed services?

Re: OpenFeature – a vendor-agnostic, community-driven API for feature flagging

#8

Post by MeteorMarc » Fri, Oct 25, 2024, 5:48 AM UTC

sabedevops wrote: post #5

Where is the tldr? Anyone familiar…what does this do and why do we care about it being standards based?

https://openfeature.dev/docs/reference/intro/

Re: OpenFeature – a vendor-agnostic, community-driven API for feature flagging

#9

Post by martypitt » Fri, Oct 25, 2024, 6:01 AM UTC

abrahms wrote: post #4

sgammon wrote: post #3

java version embeds lombok symbols lol

Forgive my ignorance, but what should it be doing instead?

Lombok is a very divisive framework in Java, with strong opinions on both sides.

Given that, it's a bold choice to include Lombok in a library that other developers will pull into their stack - it's likely to make this a non-starter from those in the 'no' camp.

As Lombok is just compiler sugar, when building an SDK for other developers, it's probably less alienating to just write the boilerplate that Lombok saves you from.

Re: OpenFeature – a vendor-agnostic, community-driven API for feature flagging

#10

Post by taveras » Fri, Oct 25, 2024, 6:07 AM UTC

sabedevops wrote: post #5

Where is the tldr? Anyone familiar…what does this do and why do we care about it being standards based?

This is a “standard” SDK for feature flags, allowing you to avoid vendor lock-in.

i.e., using feature flag SaaS ABC but want to try out XYZ? if you’re using ABC’s own DDK, refactor your codebase.

I appreciate that you can use the OpenFeature SDK with environment variables, and move into a SaaS (or custom) solution when you’re ready.