You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the KafkaFlow framework uses the IMessageSerializer and IMessageCompressor interfaces to handle both serialization/deserialization and compression/decompression of messages. While this approach has served us well, it can be more flexible and maintainable to split these interfaces into four separate interfaces: ISerializer, IDeserializer, ICompressor, and IDecompressor. This change will provide a more granular and specialized approach to message handling, improving code readability and maintainability.
Describe the solution you'd like
We propose splitting the existing IMessageSerializer and IMessageCompressor interfaces into the following four interfaces:
ISerializer
This interface will be responsible for message serialization.
IDeserializer
This interface will handle message deserialization.
ICompressor
This interface will be used for message compression.
IDecompressor
This interface will handle message decompression.
Each of these interfaces will have its own specific responsibilities, making it easier to implement and customize message handling based on the requirements of individual use cases.
Are you able to help bring it to life and contribute with a Pull Request?
Yes
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is your request related to a problem you have?
Currently, the KafkaFlow framework uses the
IMessageSerializer
andIMessageCompressor
interfaces to handle both serialization/deserialization and compression/decompression of messages. While this approach has served us well, it can be more flexible and maintainable to split these interfaces into four separate interfaces:ISerializer
,IDeserializer
,ICompressor
, andIDecompressor
. This change will provide a more granular and specialized approach to message handling, improving code readability and maintainability.Describe the solution you'd like
We propose splitting the existing
IMessageSerializer
andIMessageCompressor
interfaces into the following four interfaces:ISerializer
IDeserializer
ICompressor
IDecompressor
Each of these interfaces will have its own specific responsibilities, making it easier to implement and customize message handling based on the requirements of individual use cases.
Are you able to help bring it to life and contribute with a Pull Request?
Yes
Additional context
No response
The text was updated successfully, but these errors were encountered: