Adding BulkSink for streaming writes #441
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.
Customer is facing some latency issues because their streaming workload at steady-state is small (like about 4 documents/second) but during some periods of the day can goo to tens -of-thousand of documents - when the AsyncConnection based write stream implementation doesn't work fast and robust enough.
An initial attempt to use readStream.forEachBatch and then write each micro batch to cosmos via batch write works but is showing higher latency for the small stead-state workload.
From my own tests the latency with the BulkSink can be improved by 200-300ms (still about 200ms slower than point writes via Async Connection but that is about the expected ballpark).