Let's say I have an API gateway that talks to database micro services which have version 0.
And in version 0, the query takes a case class with 3 parameters like so: case class Query(param1: String, param2: Int, param3: Long) I want to know what happens when I change the under of params in this query case class such that in version 1, it becomes: case class Query(param1: String, param2: Int, param3: Long, param4: Byte) Does the *serialization *(either manually or write a custom deserializer per version) handle this situation when the the case class is deserialized (e.g./ protobuf)? The service implementations are naturally going to change over the course of time, how do developers using Akka, handle these protocol changes over time? From my reason, it seems to be a simple case of serialization when using clusters. This is much easier than REST apis that require a much more tedious versioning. Am I correct? -- >>>>>>>>>> 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.
