Hi, I am building micro services using akka-cluster in Java. I am using romix-kryo serialization. For this purpose I have defined Request/Response classes for every pair of request and response.
In this kind of approach I have to provide serailization configuration for every pair of request/response and well as I need to provide POJOs for every request/response required in the context. *for example:* *Actor EmployeeService needs data from actor EmployeeRepository (both running in cluster), It will send a message (i.e. object of EmployeeRepositoryRequest) to EmployeeRepository actor and in response to the request EmployeeRepository actor sends EmployeeRepositoryResponse object (Same as we do in monolithic applications).For this purpose I need to provide EmployeeRepositoryRequest and EmployeeRepositoryResponse classes in both micro services and I also need to provide the configuration for serialization for both the classes in both the actors.* But this approach is leading to a situation where the micro services (running as akka nodes in akka-cluster) are overlapping with each other (in terms of common classes and serialization configuration). When our application grows and if an actor has to communicate with multiple other actors, then one may need to add all the required serialization configurations and also need to provide all request response classes on the classpath. I am interested to know if someone is using some other approach for this purpose. Thanks in advance. -- >>>>>>>>>> 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.
