Skip to content

doc: No longer suggest Kryo serialization - #31448

Merged
johanandren merged 2 commits into
akka:mainfrom
leviramsey:kryo-doc
Jun 28, 2022
Merged

doc: No longer suggest Kryo serialization#31448
johanandren merged 2 commits into
akka:mainfrom
leviramsey:kryo-doc

Conversation

@leviramsey

Copy link
Copy Markdown
Contributor

These recommendations are likely vestiges of a pre-Jackson past.

Kryo as a serialization format is likely still OK for remoting serialization, but its maintainers have stated that they do not want to have backward/forward-compatibility hold back development, which makes its use for persistence problematic as any version upgrade may render persisted states/events unreadable. A Chill maintainer has commented that one "should never store kryo data beyond the life of a single process".

If you have used Kryo as a persistence serialization, it is recommended to explore other serialization options.

The use of Kryo to serialize data which is expected to be deserialized by a process not running at the time of the serialization is not recommended.

@octonato octonato left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @leviramsey

@johanandren
johanandren merged commit 5146f60 into akka:main Jun 28, 2022
@johanandren johanandren added this to the 2.6.20 milestone Jun 28, 2022
@patriknw

Copy link
Copy Markdown
Contributor

thanks

@leviramsey
leviramsey deleted the kryo-doc branch June 28, 2022 16:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants