Delay/avoid payload deserialization on non-matching CloudEvents with binary mode #51320
Unanswered
lmartella1
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
In our application, we use SmallRye Reactive Messaging to build streaming microservices that communicate over Kafka, and we plan to adopt CloudEvents in binary format.
We want our processors to handle only those events that match specific criteria in the incoming CloudEvents metadata (for example, events with a particular type or source). To optimize performance, we aim to avoid unnecessary deserialization for messages that do not meet these criteria.
Currently, we rely on the automatic deserialization provided by reactive-messaging, which uses auto-discovery mechanisms.
Is it possible to defer or conditionally apply deserialization based on certain CloudEvents properties, such as type or source, so that only relevant messages are deserialized and processed?
Beta Was this translation helpful? Give feedback.
All reactions