Revamp and simplify conversation management #153
Merged
Conversation
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
We had a complicated mechanism that relied in feature flags based on presence of services, split storage between message and conversation, forced sequencing outside of the pipeline configuration, etc. This revamp achieves the following: - Single handler and extension method to configure conversations `UseConversation`. - Single storage manager that uses a two-strategy approach: * Table storage for active conversation header and individual messages * Blob storage for full conversations (due to size restrictions on table storage that may be hit). - Honoring the user's preference in the pipeline where the conversation loading/restoring happens: we're now just a regular handler like any other. We also make the target storage account pluggable via DI, but with a sensible OOB default that leverages the built-in AzureWebJobsStorage setting which is already being used by the queue and table for deduplication.
Member
Author
|
🧪 Details on Ubuntu 24.04.2 LTSfrom dotnet-retest v0.7.1 on .NET 8.0.17 with 💜 by @devlooped |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
We had a complicated mechanism that relied in feature flags based on presence of services, split storage between message and conversation, forced sequencing outside of the pipeline configuration, etc.
This revamp achieves the following:
UseConversation.We also make the target storage account pluggable via DI, but with a sensible OOB default that leverages the built-in AzureWebJobsStorage setting which is already being used by the queue and table for deduplication.