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

When using additional serializers, Reply using the incoming message serialization format #6759

Open
mauroservienti opened this issue Jun 7, 2023 · 0 comments

Comments

@mauroservienti
Copy link
Member

Describe the suggested improvement

Is your improvement related to a problem? Please describe.

When using multiple serialization formats in a system, for example, when migrating a system to a new serialization format, the endpoint might get upgraded to use serializers A and B. It receives a message from another endpoint still configured to use only B. If the receiving endpoint replies, the reply message will be serialized using A, and it'll not be deserializable for the endpoint not yet upgraded to use multiple serialization formats.

Describe the suggested solution

Reply using the incoming message serialization format instead of the default one.

Describe alternatives you've considered

Stopping the system and upgrading all endpoints simultaneously to use more than one serializer.

Additional Context

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant