I really like the ease of calling remote methods using Java RMI, but the verbosity of its serialization format is a serious kill buzz (yes, I appreciated, thanks). It seems that the architects at Sun made an obvious right when developing the RPC (fluent-speaking) component, but pulled out an epic failure when it came to implementing serialization.
And vice versa, it seems that architects Thrift, Avro, Kryo (especially), protocol buffers (not so many), etc., as a rule, made an obvious right when developing their serialization formats, but either did not provide the RPC mechanism to provide that is overly confusing (or immature), or another that is more focused on transferring data than using remote methods (great for many purposes, but not for what I'm looking for).
So the obvious question is: how can I use the appeal of the RMI method-call-method, but use one of the above libraries for the wire protocol? Is this possible without a lot of work? I evaluate one of the above libraries too harshly (NB, I really dislike code generation, in general, I don’t like unnecessary annotations somewhat, and the XML configuration is a little more, any kind of “beans” makes me cringe - I don’t need weight, in ideally, I just want to implement an interface for my remote objects, as is the case with RMI).
source
share