Hello, I'm trying to devise a system which resembles a bunch of micro services or nodes. Each micro service is assigned to one or many nodes. A bunch of micro services will be the masters receiving work requests from the REST(spray.io) micro services and notifications from the worker micro services for work.
An example micro service is the security service. This will receive a case class asking to verify a user/password combination, will talk to cassandra, cache the information in the service(an actor) and then return the result back to the calling actor(the REST layer). I want to be able to add new services and update existing services without impacting on access to the REST layer for the users. I have a number of questions 1) If I use an akka node for each service then isn't the Actor system going to be resource heavy? http://doc.akka.io/docs/akka/2.3-M2/general/actor-systems.html 2) If I use routers then the code for each routee(worker micro service) needs to be on most if not every node, depending on how many nodes I want the micro service to run on. Is it a good idea to have the micro services in their own node or is it better to consolidate the micro services into one node? The drawback with this is that separate teams can't develop their own micro services. The routers would only be used to create and supervise the worker micro services; Can anybody see anything wrong with this system? -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: http://akka.io/faq/ >>>>>>>>>> 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/groups/opt_out.
