Projects tagged ‘distributed’, ‘middleware’, and ‘performance’


Jump to tag:

Projects tagged ‘distributed’, ‘middleware’, and ‘performance’

Filtered by Project Tags distributed middleware performance

Refine results Project Tags clustering (7) soa (6) j2ee (6) enterprise (5) messaging (5) distributed_computing (5) java (5) jms (5) transactions (4) integration (4) javaee (4) server (4)

[8 total ]

50USERS
   

Apache ActiveMQ is a fast Message Bus which supports many Cross Language Clients and Protocols and many advanced features while fully supporting JMS 1.1 and J2EE 1.4.

16USERS
   

Apache Camel is a powerful rule based integration framework which provides a POJO based implementation of the Enterprise Integration Patterns using an extremely powerful fluent API (or declarative Java Domain Specific Language) to configure routing ... [More] and mediation rules. The Domain Specific Language means that Apache Camel can support type-safe smart completion of routing rules in your IDE using regular Java code without huge amounts of XML configuration files; though Xml Configuration inside Spring is also supported. [Less]

13USERS
 

JORAM (Java Open Reliable Asynchronous Messaging) is an open source implementation of the JMS (Java Message Service) 1.1 API.

9USERS
   

Fura is a self-contained grid middleware that allows the grid enablement and distribution of applications on heterogeneous computational resources. Fura features a web-based GUI, wizard-guided installation and configuration, and Web Services ... [More] compliance. Fura's component based plug-in architecture allows grid services to be extended or replaced, and new services can be developed reusing existing components. [Less]

3USERS
   

JBoss Messaging was designed and built from the ground up and was not based on the JBoss MQ architecture and is 100% JMS Compliant The main new features are related to clustering functionality. JBoss Messaging contains a fully functioning and ... [More] highly scalable clustering implementation. Unlike JBoss MQ, JBoss Messaging does not rely on a "HA Singleton", this was a major drawback in JBoss MQ, where only one JMS server in the cluster was active at any one time, providing a scalability bottleneck. With JBoss Messaging this limitation disappears and all nodes in the cluster can simultaneously host active JMS servers allowing the load to be distributed much more smoothly. [Less]

2USERS
 

The MPI Testing Tool (MTT) is a project initiated by the Open MPI project for comprehensive, distributed testing of MPI software packages. MTT is designed to be run in a fully automated fashion (e.g., able to be run via cron on a regular basis). It ... [More] focuses on providing correctness and performance testing across many different impementations and versions of MPI software. The Open MPI Project uses MTT mainly for nightly regression testing of its own software, but also uses it for performance comparisons to other MPI implementations. Note that MTT is not dependent on/does not require Open MPI. [Less]

0USERS
 

FUSE Message Broker is an open source, enterprise version of Apache ActiveMQ. This enterprise release is tested, certified and supported. FUSE Message Broker is a JMS platform providing high performance, unlimited scalability, and mission-critical ... [More] reliability for distributed enterprise computing. FUSE Message Broker is a cost-effective and flexible messaging platform for reliably executing transactions and moving data, efficiently scaling operations, and connecting processes across heterogeneous database and application environments. FUSE Message Broker supports JMS 1.1 and many integration-related standards including JDBC, JCA, and EJBs; dependent specifications such as JTA and JNDI; as well as AJAX, REST, HTTP, TCP, SSL, NIO, UDP, multicast, JGroups and JXTA transport protocols. [Less]