ref(server): Build pipeline-like control flow for processing #635
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.
Refactors the envelope and event processing code by splitting the main processing function into mostly independent pipeline steps that all operate on a state. The state is mutated by each function, which can be thought of as passing it from one pipeline step to the next.
From the top-level process function, it becomes immediately clear, which actions are applied with processing and which are skipped. The stages only required for processing are conditionally compiled.
There is no change in Relay's behavior. However, there are a few changes internally:
enforce_quotas
is called on every envelope in the pipeline. This prepares the pipeline for rate limiting of items other than events. At the moment, it skips all envelopes without events and still assumesDataCategory::Error
for all events.