[jira] [Commented] (REEF-504) Clean up Serializable in Vortex

["Markus Weimer (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/REEF-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14640588#comment-14640588 ] 

Markus Weimer commented on REEF-504:
------------------------------------

As far as I understand Vortex, you have two kinds of serialization:

  1. Code serialization as a means to send tasklets to Evaluators. If you want this to be seamless for users, you'd have to user {{Serializable}}, I suppose. We had this design in a very early version of REEF, but moved to Tang because shipping live objects across the wire can't really be made safe. On the other hand, it is mightily attractive from a usability perspective. {{Evaluator.Run(new Task()))}} is so much nicer than filling out {{Configuration}} instances :-)
  2. Data serialization: For this, we've had good success with Apache Avro.

> Clean up Serializable in Vortex
> -------------------------------
>
>                 Key: REEF-504
>                 URL: https://issues.apache.org/jira/browse/REEF-504
>             Project: REEF
>          Issue Type: Sub-task
>          Components: Vortex
>            Reporter: John Yang
>
> We should avoid Serializable in Vortex user api as much as possible
> * Serializable is slow
> * Serializable restricts user code
> * We should avoid redundant serialization/sending of same classes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)