> > Are you thinking of running one JVM for each micro service? The JVM is > very heavy, and you can only run a few on each server machine (depends on > the hardware of course). > > It was late last night/early morning that I was thinking of a JVM per micro service. I forgot about the JVM overhead.
> If you need to update (restart) the services independent of each other you > will most likely want to one JVM per service (or group related services > that can be restarted together). > > I don't need but wanted to update services independently so I can keep the REST services running. > You can run several actor systems in the same JVM. An ActorSystem is heavy > compared to actors. A few threads and some 10MB of heap memory. > I think I'm better off thinking in terms of an akka cluster than a bunch of micro services. > > If you have an overall design that takes this into account it should not > be a problem to develop the services separately and then package and deploy > them in one ActorSystem. > Yes I was thinking the same as I was driving to work. Regards, Patrik Thanks Patrick. -- >>>>>>>>>> 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.
