You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: openfeature-provider/js/README.md
+64-7Lines changed: 64 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -138,15 +138,72 @@ The provider periodically:
138
138
139
139
---
140
140
141
-
## Sticky Assignments
141
+
## Materialization Stores
142
142
143
-
The provider supports **Sticky Assignments** for consistent variant assignments across flag evaluations.
143
+
Materialization stores provide persistent storage for sticky variant assignments and custom targeting segments. This enables two key use cases:
144
144
145
-
**📖 See the [Integration Guide: Sticky Assignments](../INTEGRATION_GUIDE.md#sticky-assignments)** for:
146
-
- How sticky assignments work
147
-
- Server-managed storage (zero configuration)
148
-
- Latency considerations
149
-
- Custom storage options (currently Java-only, coming soon to JavaScript)
145
+
1.**Sticky Assignments**: Maintain consistent variant assignments across evaluations even when targeting attributes change. This enables pausing intake (stopping new users from entering an experiment) while keeping existing users in their assigned variants.
146
+
147
+
2.**Custom Targeting via Materialized Segments**: Precomputed sets of identifiers from datasets that should be targeted. Instead of evaluating complex targeting rules at runtime, materializations allow efficient lookup of whether a unit (user, session, etc.) is included in a target segment.
148
+
149
+
### Default Behavior
150
+
151
+
⚠️ Warning: If your flags rely on sticky assignments or materialized segments, the default SDK behaviour will prevent those rules from being applied and your evaluations will fall back to default values. For production workloads that need sticky behavior or segment lookups, implement and configure a real `MaterializationStore` (e.g., Redis, DynamoDB, or a key-value store) to avoid unexpected fallbacks and ensure consistent variant assignment.
152
+
153
+
### Remote Materialization Store
154
+
155
+
For quick setup without managing your own storage infrastructure, enable the built-in remote materialization store:
0 commit comments