Make less decide requests when enriching events #72
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When
sendFeatureFlags
istrue
, the client makes aDecide
requests to get the latest feature flags in order to enrich the captured event with the current feature flag values.However, when processing a batch, it doesn't make sense to make a decide request multiple times for the same
distinctId
. This PR adds an in-memory cache that lasts for the duration of the batch.So far, I don't think a lot of the other client libraries actually use the
/batch
endpoint to batch requests. And if they do, I don't think they're caching/decide
requests. This is a change I'd like to consider doing for all of the clients.