[
https://issues.apache.org/jira/browse/TINKERPOP-1942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16508314#comment-16508314
]
Florian Hockmann commented on TINKERPOP-1942:
---------------------------------------------
When we're talking about switching to another - already existing -
serialization format then I wonder whether
[protobuf|https://developers.google.com/protocol-buffers/] wouldn't be the
better choice. It's a binary format that is very widely used ([~27k stars on
GitHub|https://github.com/google/protobuf]), supports [many
languages|https://github.com/google/protobuf#protobuf-runtime-installation] and
it generates the data classes already for the different languages which reduces
the amount of work someone has to do to develop a TinkerPop driver for another
language.
> Binary serialization format
> ---------------------------
>
> Key: TINKERPOP-1942
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1942
> Project: TinkerPop
> Issue Type: Improvement
> Components: io
> Reporter: Jorge Bay
> Priority: Major
>
> We should provide a binary serialization format designed to reduce
> serialization overhead and minimizing the size of the payload that is
> transmitted over the wire.
> It could be implemented in a very similar way as Kryo support but with
> interoperability in mind and ultimately we could fade Gryo out, as now with
> the GLVs it doesn't have a role to play.
> The main benefit would be the performance improvement, making serialization
> and deserialization processing time negligible on both the server and the
> client.
> Background:
> https://lists.apache.org/thread.html/13e70235591853801bab16ed457ee4f56f3dfe2d1c5817c34a036408@%3Cdev.tinkerpop.apache.org%3E
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
