> On 5 April 2012 13:16, Branko Juric <branko.ju...@gmail.com> wrote:
>> Yeh, a distributed messaging system with high availability, scalability,
>> resiliency, stability, etc.. I've worked at several companies that are
>> trying to achieve this with various types of middleware and they're still
>> struggling. This is where I hope akka will shine, but I haven't seen or
>> heard of any real examples. In Melbourne at least, I think industrial
>> strength scala + akka is what it's gonna take to get scala into the (dare I
>> say enterprise) mainstream.

>> On 05/04/2012, at 12:31 PM, Jem <jem.maw...@gmail.com> wrote:

>> In that case, what I have always wondered about is how to recreate MDBs with
>> Akka in a way that is dynamically scalable and highly available. i.e. how to
>> process messages from a single queuing system, growing and shrinking across
>> multiple machines as necessary, without having any single machine as a point
>> of failure.

>> Jem

>> On 5 April 2012 12:25, Ben Hutchison <brhutchi...@gmail.com> wrote:

>>> On Thu, Apr 5, 2012 at 1:19 AM, Toby Corkindale <t...@dryft.net> wrote:
>>>> For Akka, or just in general, I'd love to see more practical examples
>>>> for programming with Scala.
>>>> Not just synthetic problems to practice using collections or the type
>>>> system, but real-world problems where Scala allows much more elegant
>>>> or higher-performing solutions.

>>> For Scala generally, Twitter is the best example that comes to mind -
>>> they open source lots of their Scala-based enterprise systems:

>>> https://github.com/twitter/repositories

>>> As for Akka especially, a big "me too". Thats one of my big concerns
>>> with Akka. It seems to be "tech first, projects later". The talks Ive
>>> been on akka, on the net and at YOW, always talk about it's tech from
>>> an almost theoretical standpoint, not in the context of particular
>>> use-cases & applications.

>>> -Ben

>>> --
>>> You received this message because you are subscribed to the Google Groups
>>> "Melbourne Scala User Group" group.
>>> To post to this group, send an email to scala-melb@googlegroups.com.
>>> To unsubscribe from this group, send email to
>>> scala-melb+unsubscribe@googlegroups.com.
>>> For more options, visit this group at
>>> http://groups.google.com/group/scala-melb?hl=en-GB.

>> --
>> You received this message because you are subscribed to the Google Groups
>> "Melbourne Scala User Group" group.
>> To post to this group, send an email to scala-melb@googlegroups.com.
>> To unsubscribe from this group, send email to
>> scala-melb+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/scala-melb?hl=en-GB.

>> --
>> You received this message because you are subscribed to the Google Groups
>> "Melbourne Scala User Group" group.
>> To post to this group, send an email to scala-melb@googlegroups.com.
>> To unsubscribe from this group, send email to
>> scala-melb+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/scala-melb?hl=en-GB.

> --
> Turning and turning in the widening gyre
> The falcon cannot hear the falconer
> Things fall apart; the center cannot hold
> Mere anarchy is loosed upon the world

> --
> You received this message because you are subscribed to the Google Groups "Melbourne Scala User Group" group.
> To post to this group, send an email to scala-melb@googlegroups.com.
> To unsubscribe from this group, send email to scala-melb+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/scala-melb?hl=en-GB.