Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality. Learn more →
FF4J Alternatives
Similar projects and alternatives to FF4J
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
javaslang-circuitbreaker
Resilience4j is a fault tolerance library designed for Java8 and functional programming
-
-
Modern Java - A Guide to Java 8
Modern Java - A Guide to Java 8
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Codename One
Cross-platform framework for building truly native mobile apps with Java or Kotlin. Write Once Run Anywhere support for iOS, Android, Desktop & Web.
-
-
-
-
flagsmith
Open Source Feature Flagging and Remote Config Service. Host on-prem or use our hosted version at https://flagsmith.com/
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
FF4J reviews and mentions
-
FF4J – Feature Flags for Java
https://github.com/ff4j/ff4j/blob/v1/ff4j-core/src/main/java...
> The feature will be flipped after release date is reached.
Don't ever use this. This is a "time bomb". This is a very bad idea. It's basically like scheduling a time for your app to go down when you aren't paying attention.
You have to have a human in the loop. The right way to "schedule a release" is to have a human flip the flag at the appropriate time (preferably, ramp it up to 100% of users gradually) and then stay online for a little while to do an emergency ramp down if/when things go bad (that weren't caught by some automated system in the ramp up).
I believe he means doing a rollout to 30% of users and having that be consistent, so that the same 30% of users are always in the flag, not just 30% of evaluations.
This is typically achieved by hashing the flag+userId, converting to an integer and dividing by Max.integer.
I see https://github.com/ff4j/ff4j/blob/main/ff4j-core/src/main/ja... which looks like a rollout for 30% of evaluations but I don't see what you're looking for. I may well be looking in the wrong spot.
Yikes:
> the behavior of a feature can be enslaved with your custom implementation
- We create an open-source feautre flag sytem to help release faster and safe
-
A note from our sponsor - InfluxDB
www.influxdata.com | 28 Mar 2024
Stats
ff4j/ff4j is an open source project licensed under Apache License 2.0 which is an OSI approved license.
The primary programming language of FF4J is Java.