wso2 esb for university services
April 26, 2016

wso2 esb for university services

Anonymous | TrustRadius Reviewer
Score 6 out of 10
Vetted Review
Verified User

Overall Satisfaction with WSO2 Enterprise Service Bus

We use WSO2 enterprise service bus to orchestrate and integrate business services offered to universities.
  • It's really easy to install for a quick evaluation.
  • Open source. This is a must in our company.
  • It's highly scalable. Adding computing nodes is really straightforward.
  • Good product support, quick and effective.
  • While it's easy to configure for a quick start, it is not so easy to deploy by yourself in a complex production scenario.
  • Not very stable for production usage, we encountered several trivial bugs that make us believe that this product is still not widely adopted.
  • Lack of a built in mechanism for auto-restart in case of an application server crash.
  • For developers it gave us the ability to wrap legacy services with little effort.
  • From an architectural/ sysadm point of view WSO2 application server is very different to manage than the other java application server we were using in our company, so the initial effort has been huge.
We previously used the Oracle Weblogic solution, but:
- it was more expensive
- it's not open source
- it's more complex to manage
Wso2 carbon products are well suited for a devops scenario. Once you've found the right recipe for your company it's then really straightforward to replicate or extend installation.

Using WSO2 Enterprise Service Bus

10 - System integrators
4 - Two people for development support
Two people in the operations team

Evaluating WSO2 Enterprise Service Bus and Competitors

Yes - Oracle weblogic service bus
  • Price
  • Third-party Reviews
Our company embraced the open source philosophy, so we decided to pass to an open source product.
No, we're satisfied of our choice

WSO2 Enterprise Service Bus Training

The documentation is quite extensive, but starting from scratch is not straightforward. A cookbook with some example architectures would be great.

Configuring WSO2 Enterprise Service Bus

For sure very complex
No - we have not done any custom code

WSO2 Enterprise Service Bus Support

Our experience with the WSO2 support has beent satisfactory
Quick Resolution
Good followup
Knowledgeable team
Problems get solved
Kept well informed
No escalation required
Immediate help available
Quick Initial Response
Yes - yes, fortunately it wasn't a new bug, so the solution was just ready
Once we were experiencing an annoyng memory consumption problem that made our production enviroment unstable and support was able to give us precious advice that allowed us to resolve the problem quickly.

Using WSO2 Enterprise Service Bus

Compared to competitors the overall experience has been fine
Well integrated
Requires technical support
Slow to learn
Feel nervous using
Lots to learn
  • Scalabilty
  • All the configurations are file-based, so it's well suited for automated deployment
  • Lack of auto-restart built-in capabilities
  • No ajp proxy support

WSO2 Enterprise Service Bus Reliability

Adding a server node is really straightforward, there are just few point in the configuration files.
Lack of auto-restart built-in capabilities. In case of running out of memory there are no built-in methods to recover from a crash, just for example, Oracle WebLogic Node Manager.
The product is performing well and consuming few resources

Upgrading WSO2 Enterprise Service Bus

Yes - The upgrade has been very hard, since we were upgrading from the stratos version to the stand-alone one
  • ESB 4.9.0 abandoned the Wso2 Elastic load balancer, and allowed us to use Apache Web Server
  • No more stratos manager required
  • More stable
  • configuration file rationalization