Hi, thank you very much for your suggestions. At the beginning, I thought that 
protobuf needed to write a .proto file to describe the serialization format, 
which always felt troublesome. Protostuff is a serialization method based on 
protobuf. Compared with protobuf, the most obvious advantage is that we do not 
need to write .proto files to achieve serialization with almost no loss of 
performance, so I did not consider protobuf, but considering our current 
scenario, maybe protobuf is a way for us Very good solution. I will benchmark 
these solutions (protostuff, protobuf, Kryo, Hessian), and then the decision 
will be made by the community (performance and community activity and other 
factors determine which method to use).


Thanks again for your suggestions.


Best  wishes!
CalvinKirs


On 12/7/2020 20:17,Sheng Wu<[email protected]> wrote:
Why protobuf not included in the list? This is definitely widely used today
in cloud-native related things.


Sheng Wu 吴晟
Twitter, wusheng1108


CalvinKirs <[email protected]> 于2020年12月7日周一 下午6:54写道:

I will benchmark the three serialization methods of protostuff, kyro, and
hessian. Do you have any other suggestions?


Best  wishes!
CalvinKirs


On 12/6/2020 23:08,lidong dai<[email protected]> wrote:
Do you have any suggestions?



Best Regards
---------------
DolphinScheduler(Incubator) PPMC
Lidong Dai 代立冬
[email protected]
---------------


On Mon, Nov 16, 2020 at 10:08 AM CalvinKirs <[email protected]> wrote:



Hi, DolphinScheduler community.
We released netty as a communication component between master and worker
in version 1.3. This is a great feature. Therefore, I hope to further
enhance this foundation and add more effective serialization methods. For
example, Kryo, Hessian or proststuff, it is easier for individuals to
purchase protostuff. If possible, I will benchmark and choose the most
suitable serialization method on this basis.


Welcome everyone to discuss whether you need to add a more efficient
serialization method. thank you very much!
Best  wishes!
CalvinKirs



Reply via email to