Skip to content

doc: No longer suggest Kryo serialization #31448

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
johanandren merged 2 commits into from
Jun 28, 2022
Merged

doc: No longer suggest Kryo serialization #31448

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9da5131
Document Kryo suitability
leviramsey Jun 24, 2022
20e8fe5
Don't recommend at all
leviramsey Jun 24, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 0 additions & 6 deletions akka-docs/src/main/paradox/serialization.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -278,12 +278,6 @@ switch to the new serializer.
As an optional third step the old serializer can be completely removed if it was not used for persistent events.
It must still be possible to deserialize the events that were stored with the old serializer.

## External Akka Serializers

* [Kryo serializer for Akka](https://github.com/altoo-ag/akka-kryo-serialization)

* [Twitter Chill Scala extensions for Kryo](https://github.com/twitter/chill)

### Verification

Normally, messages sent between local actors (i.e. same JVM) do not undergo serialization. For testing, sometimes, it may be desirable to force serialization on all messages (both remote and local). If you want to do this in order to verify that your messages are serializable you can enable the following config option:
Expand Down