Replies: 1 comment 1 reply
-
|
This is what serialization id's are for, Hazelcast should take care of all of this. |
Beta Was this translation helpful? Give feedback.
-
|
Well it started from the fact that the Frank!Flow with its new backend isn't compatible with older versions of the framework. Just like an API it is probably a smart idea to keep versions so applications using it can keep on understanding each other even if there was a breaking change. |
Beta Was this translation helpful? Give feedback.
-
We should have a way to identify that modules/applications that communicate over the frankframework-gateway are compatible with each other, for example that the deployed version of the frank-flow works with gateway deployed by the framework.
A good way to do this is through protocol versioning.
The applications that communicate through the gateway should tell the gateway what protocol version they are using, if the gateway doesn't support a certain version, because it's too old or maybe newer than the deployed gateway can handle, then the gateway should send back a special message for those applications to handle.
Having some sort of protocol versioning solves the issue that applications aren't compatible with other applications using the gateway or the gateway itself, this also gives back a more useful error or logging that can inform the people deploying and managing these applications.
Beta Was this translation helpful? Give feedback.
All reactions