Well, my name may not be Victor, but let me give it a shot ;), since I
actually had to work on similar thing on the unrelated product.
Akka is a framework and a programming model. This means it could be used as
part of any of your existing application (Web, Console etc.) or your new
application could itself be Akka-based from the get go.
Now, if I am including Akka as part of my WAR, then I would most definitely
include akka/scala and related JARs in the WAR's classpath (e.g., lib
directory). Its simple and straight forward since WAR deployment/runtime
model and backing application server does the rest (e.g., creates app class
loader, loads classes as needed, starts the app etc.) as long as you follow
the conventions the underlying model dictates.
But what about stand alone? Suddenly all of these concerns that the
developer didn't have to worry about by relying on some standard
development/deployment/runtime model are back to be the concerns of such
developer. Sure we are all (or some of us) smart and bright enough to take
care of it . . . create our own launcher, make it classpath-aware, possibly
even creating a dedicated classloader to support multiple and isolated
deployments within the single JVM. It's certainly not the most difficult
task, but why? Why do I need to worry about it every time I have a
standalone app requirement? The concerns would most likely be the same and
having framework to address them is not such a bad idea. In fact its not
even original. Lots of frameworks have this.
Having said that, I'll attempt to guess that your disappointment with
Akka's Microkernel has more to do with it laking certain features that you
want/need. Again, just a guess, but if so, then may be the real question
should be more related to discussing such missing features or patches to
the existing features.

Cheers
Oleg



On Wed, Jan 22, 2014 at 12:55 PM, Michael Pavlovsky <
[email protected]> wrote:

> 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.
>

-- 
>>>>>>>>>>      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.

Reply via email to