Custom Serialization with FST or Kryo ?

[kraythe]

Has anyone used FST Serialization[1] with their Akka messages? If so, how did it work out? I am debating using this or Kryo for serialization and FST seems to be faster and more "drop-in" compliant so i was curious if anyone had tried it. If you have tried Kryo before I would be interested in your experience. Id like to stay away from Java serialization and protobuf is a non-starter as I have tons of code I am moving to akka that I can't just re-engineer. 

Thanks.

-- Robert

[1] https://github.com/RuedigerMoeller/fast-serialization

[Любен]

Have you tried Akka-Kryo-Serializatio[1] ? It should work out of the box with "default" or "automatic" id-strategy. And it has other optional parts that may come handy, e.g. transparent compression using LZ4 or AES encryption.

Regards,

luben

[1] https://github.com/romix/akka-kryo-serialization

--
>>>>>>>>>> Read the docs: http://akka.io/docs/
>>>>>>>>>> Check the FAQ: http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user
---
You received this message because you are subscribed to the Google Groups "Akka User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+...@googlegroups.com.
To post to this group, send email to akka...@googlegroups.com.
Visit this group at https://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

[Bert Robben]

I'm using FST for serialization and am happy with it. It works reasonably out-of-the-box.

To get it to work with remoting, I had to register specific FST serializers for ActorRef and Deploy. The first one falling back to Serialization.serializedActorPath and the latter one delegating to the default Akka serializer (using SerializationExtension.get(system).serializerFor(clazz)).

I haven't used kryo, so I can't compare with it.

Bert