Project Description
Reactor Service Bus is a light weight .Net service bus built upon the Apache NMS messaging API. It provides a rich subscription model and built in load balancing features for consumers.
The Reactor Service Bus isn't just another .Net service bus. Although it provides a similar programming interface to other .Net service bus frameworks on the market, it’s built upon the Apache .Net Messaging API, which allows Reactor Service Bus to connect to multiple providers or transports using a single API. NMS is modeled to implement the JMS specification, which provides powerful features not found in non-JMS based messaging brokers. Currently, Reactor Service Bus can integrate with the following transports:ActiveMQ
TIBCO EMS
MSMQ
MS WCF
Any STOMP broker
TransactionalReactor Service Bus uses standard messaging transactions to handle failures. If the handling of an incoming message fails, the bus places the message back on the queue from which it was delivered. To avoid “flip-flop” delivery, a configurable maximum number of deliveries is evaluated each time the message fails. Once this maximum number of deliveries is met, the message is placed in the dead letter queue for later intervention and processing. Easy ConfigurationAlthough Reactor Service Bus contains many extension points, it is easily configured through a succinct configuration API and conventional application configuration. Reactor Service Bus is container-agnostic and provides the following 5 adapters to integrate IoC containers for it's use: Unity
Windsor
StructureMap
Spring.Net
Ninject
Read more about how to use the adapters in the Containers section of our documentation.Simplified Programming ModelThe standard JMS programming model can be cumbersome. Imagine writing ADO.Net "plumbing" code to access all of your data. While easy to use, certain pieces of plumbing, such as connections are better abstracted. Reactor Service Bus uses a programming model similar to other .Net service bus frameworks on the market. Creating message handlers that either listen to queues or topics is as easy as implementing a simple interface and decorating the class with attributes that declaratively specify what queue or topic the message is expected on.
Read more: Codeplex
Reactor Service Bus is a light weight .Net service bus built upon the Apache NMS messaging API. It provides a rich subscription model and built in load balancing features for consumers.
The Reactor Service Bus isn't just another .Net service bus. Although it provides a similar programming interface to other .Net service bus frameworks on the market, it’s built upon the Apache .Net Messaging API, which allows Reactor Service Bus to connect to multiple providers or transports using a single API. NMS is modeled to implement the JMS specification, which provides powerful features not found in non-JMS based messaging brokers. Currently, Reactor Service Bus can integrate with the following transports:ActiveMQ
TIBCO EMS
MSMQ
MS WCF
Any STOMP broker
TransactionalReactor Service Bus uses standard messaging transactions to handle failures. If the handling of an incoming message fails, the bus places the message back on the queue from which it was delivered. To avoid “flip-flop” delivery, a configurable maximum number of deliveries is evaluated each time the message fails. Once this maximum number of deliveries is met, the message is placed in the dead letter queue for later intervention and processing. Easy ConfigurationAlthough Reactor Service Bus contains many extension points, it is easily configured through a succinct configuration API and conventional application configuration. Reactor Service Bus is container-agnostic and provides the following 5 adapters to integrate IoC containers for it's use: Unity
Windsor
StructureMap
Spring.Net
Ninject
Read more about how to use the adapters in the Containers section of our documentation.Simplified Programming ModelThe standard JMS programming model can be cumbersome. Imagine writing ADO.Net "plumbing" code to access all of your data. While easy to use, certain pieces of plumbing, such as connections are better abstracted. Reactor Service Bus uses a programming model similar to other .Net service bus frameworks on the market. Creating message handlers that either listen to queues or topics is as easy as implementing a simple interface and decorating the class with attributes that declaratively specify what queue or topic the message is expected on.
Read more: Codeplex
Posts
0 comments:
Post a Comment