Create an article "Immutable message and serialization"

[alexvaluyskiy]

Base on these articles http://getakka.net/docs/concepts/messages http://akkanetdocfx.azurewebsites.net/articles/actors/untyped-actor-api.html#messages-and-immutability

[Danthar]

You mean as a document under "Concepts" ? Or something else ?

[alexvaluyskiy]

Yes, in "concepts". I think we should have a recommendation for messages. For example

• DO create immutable messages
• AVOID using complex types which should not be designed for serialization, like Lazy, StringBuilder
• AVOID using exceptions in your messages, unless your serializer supports them
• AVOID usingobject type in your messages.
• AVOID circular references in your messages
• DO NOT create more than one constructor in a message. You serializer-provided attributes to mark a default constructor