-
Notifications
You must be signed in to change notification settings - Fork 68
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.
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
Do we want to support batch events sending #438
Comments
knative/eventing#4409 I don't think eventing generally supports the json batch format |
Yeah this is like a thought of mine based on a TODO, but the solution should be to wait for the sockets implementation? |
I'd prioritize HTTP/2 support first, then measure the improvement batch provides. |
Rationale: HTTP/1.1 Is likely encumbered by a lot of TCP setup/teardown per request, which probably imposes substantial overhead. HTTP/2 allows multiplexing requests over a single TCP pipe for the cost of a library change for clients. Adding batch delivery support requires restructuring code vs current implementations, so has a higher ecosystem cost. |
Nice! Supper clear, thanks @evankanderson |
This issue is stale because it has been open for 90 days with no |
We need to decide if we want to support the CloudEvents batch format or not, and the implement it.
The text was updated successfully, but these errors were encountered: