Repository navigation
Request-scoped lifecycle and context propagation - #110
Merged
Merged
Conversation
4 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem - Request-scoped lifecycle and context propagation
Doppar already drops resolved request-scoped services when a request terminates, but that cleanup is implicit and HTTP-only. It sweeps every service bound after boot, so the lifetime of a service depends on when it was registered, and console commands and workers get no equivalent. There was also no object that described the running request, command or job, so logs from one execution could not be tied together and metadata such as a tenant had nowhere to live.
PR for these docs