docs: lightweight deployments for akka edge #1039
Conversation
| The GraalVM Native Image tracing agent can only generate configuration for code paths that were observed during the | ||
| running of an application. When using this approach for generating configuration, make sure that tests exercise all | ||
| possible code paths. In particular, check dynamic serialization of classes used for persistence or cross-node | ||
| communication. |
There was a problem hiding this comment.
Actually, all configured serializers are loaded at startup, so it's not needed to send all messages to find them (as far as I understand). Unless there is additional reflection in the serialization library.
There was a problem hiding this comment.
Yes, serializer classes are reflectively loaded at startup. The tricky part is when the deserialization dynamically creates classes with reflection — the constructor and other methods accessed reflectively need to be in the config.
We've seen this with the samples. This was a missed scenario for deserializing existing persisted state: #1002 (comment). And here some messages were only local and didn't end up going over remoting serialization when testing: 23fc027. We may not have covered all cases ourselves for the samples — for example, I don't think I checked deserializing persisted snapshots.
Having automated reflect config will be useful for serialization.
First pass on some Akka Edge docs for what I'm calling "lightweight deployments" — covering lightweight kubernetes, OpenJ9, GraalVM native image, and multidimensional autoscaling.