Scala folks will no doubt be interested in this (see links below) - Apache ActiveMQ message broker is undergoing a rewrite. Scala 2.8 is being used and instead of Java-style threading the Scala Actor library, and particularly the React semantics, is being employed.
This is a pretty serious software that is widely used. What will be excellent is that now there will be a Scala version and a Java version that can be compared against each other. It's open source so anyone that wants to will be able to review the source code. Can't think of a better vehicle for being able to explore in earnest the question of are their positive gains in adopting Scala vs sticking with Java. Does the nature of Scala at source code level entail better story for comprehensibility, conciseness, ease of maintainability? Is Scala Actor model more effective for dealing with concurrency in software design and implementation? Does the Actor model (especially React) enable better performance giving rise to higher scalability, etc.? There's plenty more involved, such as extensible plugin aspects of AMQ - or embedded DSL languages such as Camel that is used for routing, bridging, transformations... Even the notion of the prior Java JMX rationale is being rethought due to going with Scala. The next generation of messaging broker from the Apache ActiveMQ team is being worked on, and they are about to reach a Beta 1 stage. http://activemq.apache.org/apollo/versions/1.0-beta1/website/index.html Architecture http://activemq.apache.org/apollo/versions/1.0-beta1/website/documentation/architecture.html -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
