IMO, Microkernel was a really _BAD_ idea. I have a very long list of items that i hate about it but instead of bitching I would really like to hear from Victor Klang what was the primary set of use-cases that this component was supposed to implement. Only then, one could judge its pros and cons.
*Dear Victor, please shad some light ... * P.s: when i complain i usually have the following set of aspects in my mind: deployment, monitoring, side by side provisioning , componentisation, versioning, Standard class loading, multi node clustering support , configuration loading, osgi On Tuesday, January 21, 2014 7:38:10 PM UTC-5, Peter Wolf wrote: > > Hello, > > In keeping with the "What are the advantages of XXX" theme... What does > the Microkernel add? > > How is using the Microkernel different from just running "java class"? > > I am searching for a way to deploy across a large number of Amazon > machines. These machines will be dynamically created/destroyed as I need > more bandwidth. Is Microkernel the correct tool for this problem? If not, > what should I be reading about? > > Thanks > Peter > -- >>>>>>>>>> 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.
