There is a package inside exe project io.wavebeans.execution.medium which covers serialization issues for execution. It is complete mess by itself with self-written serialization.
The point of the medium is to provide functionality for effective transferring data for pods.
Current limitations:
(for framework developer) It is very hard to add a new medium type onto the list, hence it is hard to add new types into the lib and have support of it during execution.
(for framework user) It is impossible to add custom type if any, however lib functionality allows to do this.
Despite the fact that current implementation is kinda fast (it's dumb though), it's definitely way faster than built-in java serialization, it is completely unsupportable.
What needs to be added:
Transparent way for framework developers to extend the medium list without pain. Perhaps using 3rd party libraries. What should take into consideration: current implementation heavily reuses primitive arrays, otherwise that's a lot of pressure on GC (seems so).
A way for framework users to add their own types and provide medium for this if that's required. Or better provide some generic medium by default.
There is a package inside
exeprojectio.wavebeans.execution.mediumwhich covers serialization issues for execution. It is complete mess by itself with self-written serialization.The point of the medium is to provide functionality for effective transferring data for pods.
Current limitations:
libfunctionality allows to do this.What needs to be added: