Microsoft recently announced new machine learning capabilities for Microsoft Azure platform. Developers can also create their own web services and publish them to Azure Marketplace. Microsoft also announced availability of Apache Storm for Azure. Azure Stream Analytics, Data Factory and Event Hubs for Azure were all announced in the past few weeks by Microsoft. In this article we explore moreabout
The recently released version v1.0.0 of HazelcastMQ adds a Java STOMP client and server implementation as well as an Apache Camel component. HazelcastMQ is a provider of a messaging layer on top of the basic Queue and Topic data structures in Hazelcast, an in-memory data grid. STOMP is the Simple (or Streaming) Text Orientated Messaging Protocol, an interoperable wire format.
The recently released version 5.9 of the message broker Apache ActiveMQ adds among other features support for replication of the LevelDB Store and a new Hawtio web console together with more than 200 issues resolved.
After 11 years, JMS 2.0 has been released as part of Java EE 7, with a focus on simplicity. InfoQ takes a look at some of the new features.
VMware's SpringSource team have recently announced plans for Spring 4.0, the next update to the framework, with new features including support for Java SE 8, Groovy 2, parts of Java EE 7, and WebSockets. InfoQ spoke to Spring framework co-founder Juergen Hoeller to find out more about the plans.
As JSR 342, the specification for Java EE 7, makes its way through early draft review the expert group is keen to get community feedback on a number of open issues. These include which of the new APIs should be added to the Java EE Full/Web Profile, as well as how to better align CDI with Java EE.
Apache Apollo 1.0, ActiveMQ subproject, was just released. Apollo's new threading model which is geared to multi-core microprocessors makes it faster, more scalable and more reliable than ActiveMQ. Apache Apollo now has JMS support along with a set of JMS benchmarks that show it is a clear competitor in the messaging space.
Apollo is a next generation message queuing solution that recently posted some impressive benchmarks against RabbitMQ, HornetQ, and ActiveMQ. The benchmarks indicate that Apollo will be on a lot of developer's roadmaps for messaging.
When building larger scale applications, message queues are often very helpful for both distributing and aggregating workloads. In the .NET ecosystem there are several options available for message queuing. This article highlights some of the more popular and unique offerings as well as the basic terminology needed to evaluate them.
Oracle filed the umbrella JSR for Java EE 7 last week, and the specification has now passed the initial review ballot stage. The overarching themes are emerging web technologies, cloud computing, and continued ease of use improvements including an overhaul to the JMS API. Elsewhere, JPA is scheduled to receive attention, and Oracle is talking about plans to revive the long dormant JCACHE JSR.
JBoss has published the results of messaging throughput benchmarks against the leading enterprise messaging servers on the market that implement the Java Message Service (JMS) API. In these results HornetQ demonstrates superior performance compared to the other products.
VMware business unit SpringSource announced today that it had acquired Rabbit Technologies. Rabbit Technologies is the primary sponsor of the open source RabbitMQ messaging system.
JBoss HornetQ has proven faster in peer reviewed benchmark, than the current version of ActiveMQ, mainly because of its choice to implement a highly tuned journal that uses AIO when running on Linux. ActiveMQ seems to be going the same way for version 6, pushing the competition.
A new version of the Spring.NET framework, version 1.3, was recently released. InfoQ spoke with Mark Pollack, founder and lead of the Spring.NET project, to learn more about this release and what new capabilities it brings, and also to learn more about the new Spring Integration.NET project.
W3C has just released Candidate Recommendation SOAP over Java Message Service 1.0, defining how SOAP should bind to a messaging system that supports the Java Message Service (JMS).