[go: nahoru, domu]

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.

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

Transports are responsible for batching messages #360

Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Transports are responsible for batching messages
Signed-off-by: Christoph Neijenhuis <christoph.neijenhuis@commercetools.de>
  • Loading branch information
cneijenhuis committed Dec 6, 2018
commit 4497de7fa653aad69f92e37ab47d6294f495973a
8 changes: 6 additions & 2 deletions primer.md
Original file line number Diff line number Diff line change
Expand Up @@ -114,8 +114,12 @@ and processing, of the message. Data that is not intended for that purpose
should instead be placed within the event (the `data` attribute) itself.

Along with the definition of these attributes, there will also be
specifications of how to serialize the event in different formats and
transports (e.g. JSON and HTTP).
specifications of how to serialize the event in different formats (e.g. JSON)
and transports (e.g. HTTP, AMQP, Kafka).

Batching of multiple events into a single API call is natively supported by some
transports. To aid interoperability, it is left up to the transports if and how
batching is implemented.

### Non-Goals
The following will not be part of the specification:
Expand Down