Payload converter based on payload size #442
Open
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.
This example shows how to implement a payload converter that detects when a payload is larger than a certain threshold, in which case it writes it to a storage system of choice instead of the temporal server. In this particular example payloads are written to a local file but it can be adapted to work with any storage. Such a converter is useful when a workflow/activity regularly has payloads that risk exceeding Temporal's hard limit of 2MB.
What was changed
Added a new sample.
Why?
Two places where I worked required building something similar, so I thought it would be a good idea to write a sample for it. I haven't seen a similar sample available.
Checklist
How was this tested:
Locally with Temporal cluster as well as unit tests available.
Any docs updates needed?
No