I'm trying to figure out what the best strategy for making changes to the message protocols in my cluster that will let me do upgrades while the cluster is running. I'm trying to get to a point where I have some parity in upgrades as I had when my services talked over HTTP w/JSON. I.e. as long as i was backwards compatible in my message changes, I could swap out service nodes one at a time.
Using akka-cluster as my service interconnect infrastructure, this is of course trickier. The default Java serializer pretty much dies on any changes, so the question is whether I can fix this with a custom serializer or I have to be strict and make every protocol change a new message type and keep the old and new around until all nodes are on the same new version. I figured using protobuf might do that trick, since the format itself offers this type of backwards compatibility. However, I can neither find a respository to resolve akka-protobuf-serialization from nor can I get it to build locally. And before I invest a lot of time trying to make it work, I wanted to see if anyone can confirm that its interaction with akka even lets me get the type of backwards compatibility I am hoping for. How are people generally dealing with these types of protocol evolutions in akka clusters? thanks, arne -- >>>>>>>>>> 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
