Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Investigate Dual Shipping's sequential behavior #296

Open
rayz opened this issue Nov 1, 2024 · 0 comments
Open

Investigate Dual Shipping's sequential behavior #296

rayz opened this issue Nov 1, 2024 · 0 comments
Labels
area/components Sources, transforms, and destinations. destination/datadog-metrics Datadog Metrics destination. type/chore Updates to dependencies or general "administrative" tasks necessary to maintain the codebase/repo.

Comments

@rayz
Copy link
Contributor

rayz commented Nov 1, 2024

Context

With the current dual shipping implementation in #292 , we clone the original request for each additional endpoint and fire them off sequentially.

We should consider if this behavior is needed if we optimized with parallelism with one client per resolver/API key pair.

We should also investigate if sending the requests sequentially matter, and what happens if one particular request fails.
@rayz rayz added area/components Sources, transforms, and destinations. type/chore Updates to dependencies or general "administrative" tasks necessary to maintain the codebase/repo. destination/datadog-metrics Datadog Metrics destination. labels Nov 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/components Sources, transforms, and destinations. destination/datadog-metrics Datadog Metrics destination. type/chore Updates to dependencies or general "administrative" tasks necessary to maintain the codebase/repo.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rayz