Why choose WSO2 ESB?
I've been on the hunt for choosing an ESB for a large-scale enterprise level project.
A few things I would like the ESB to be capable of:
- Interoperable with ActiveMQ/JMS
- Support deploying of services easily
- Contain a web interface for configuration/monitoring/management
- Support multiple transports http,jms,xmpp
- Support for frameworks CXF, Spring, Axis2, etc.
- Provide mediation and custom mediators
- Provide QoS
- Easy learning curve for developers
- Interoperable with Jini
- Scalable
- Useful documentation for integrators, developers and administrators
My question is:
Why should I choose WSO2 ESB over other ESBs such as FuseESB, chain builder, and JBoss?
What makes WSO2 unique over these other ESBs?
Thanks!
Bookmark/Search this post with:
- Login or register to post comments
- Printer friendly version
- 165 reads
Hi Jamie - Interoperable
Hi Jamie
- Interoperable with ActiveMQ/JMS
Yes, our default configuration and all samples are based on AMQ
- Support deploying of services easily
Yes, you can build/deploy these using the graphical management console
- Contain a web interface for configuration/monitoring/management
Yes
- Support multiple transports http,jms,xmpp
Yes, we do not yet ship the XMPP code, but its ready now
- Support for frameworks CXF, Spring, Axis2, etc.
Yes, also .Net
- Provide mediation and custom mediators
Yes, custom mediators using Java, BFS scripting languages such as Ruby, Javascript, Groovy etc and Spring
- Provide QoS
Yes, WS-RM and WS-Sec based on WS-Policy. Also supports clustered load balancing, caching and throttling
- Easy learning curve for developers
Yes, I believe so :)
- Interoperable with Jini
Not sure what you mean here
- Scalable
Yes, supports clustered deployments
- Useful documentation for integrators, developers and administrators
http://wso2.org/project/esb/java/1.7/docs/docs_index.html
>Why should I choose WSO2 ESB over other ESBs such as FuseESB, chain builder, and JBoss?
Download each of these, and try them for a simple proxy, CBR/XSLT or transport switching scenario common in your use cases. Then it will be easier for you to decide
>What makes WSO2 unique over these other ESBs?
High Performance (http://wso2.org/library/3740), being light weight, very easy to use, learn and deploy, includes a graphical management console as well as JMX support, Supports many transports and mediation actions out of the box, ships more working samples (> 55) than any other ESB.. etc
asankha
thank you for the reply, -
thank you for the reply,
- Interoperable with Jini
Ideally I want services to automatically discover, connect, and begin talking to each other without having to know where they exist on the network. Thus a service could be an agent of some sort who becomes serialized across various machines over the course of its lifetime.
In a world where ad-hoc networks are becoming dominant the discovery of other services becomes more difficult to manage. I have yet to find an ESB that addresses how services automatically discover each other in some kind of dynamic manner (either using a rule set or attribute/characteristic matching for clients and services).
I guess my question should read.
How does WSO2 solve dynamic lookup and discovery of services deployed across a single or multiple ESBs?
Hi Jamie We do not yet have
Hi Jamie
We do not yet have support for dynamic discovery with Jini.. do you know of any other ESB's that has such a capability? Most of the time, services are registered and looked up via a Registry, and we do support integration with the WSO2 Registry product or other registries through an adapter. We plan to bring in a capability to our ESB, that can automatically lookup a destination endpoint for a message from a Registry, and this could be a possible solution for your problem - if you specify the rules for the lookup etc on the ESB
asankha
hi asankha, I do not know of
hi asankha,
I do not know of any ESBs that offer dynamic discovery using Jini, or a jini-like discovery mechanism. I am currently using the WSO2 Registry, and it is excellent, however it would not offer the features I need for indexing services. Instead we use it for storing various versions of the XSDs and WSDLs of services.
Much thanks!
Hi Jamie WSO2 Registry folks
Hi Jamie
WSO2 Registry folks are implementing indexing support as we speak.. and it will be available shortly.. please do ask on the Registry forums / mailing lists or feel free to raise enhancement requests for what you would like to see.. we treat requests by users very highly :)
asankha
thank you. we likely will be
thank you.
we likely will be using the WSO2 Registry for our next project. looking forward to the new changes.