Skip to main content

What is different in WSO2 ESB compare to other integrations solutions

In my previous post , I have discussed about the facts you need to consider when selecting an integration solution for your enterprise IT infrastructure. I didn't provide any clue on what is the best vendor you can select since that depends on your requirements and budget and many other reasons. In this post, I will do a comparison between several open source and proprietary solutions and differentiate WSO2 ESB (my employer) features with them.

Proprietary ESB 


Pros 
  • Suite of solutions included and work smoothly with each other (eg: CEP, BPEL, MB, Registry)
  • Powerful and stable tooling and monitoring capabilities
  • Excellent support for price
Cons
  • High price, High complexity
  • Licensing and non-transparent pricing model
  • Different components may come from different code bases acquired through different companies
  • Heavy products
  • Installation may need consultants and take more time

Open source ESB


Pros
  • Simple installation and intuitive tooling
  • Some vendors offer free version and commercial version for price with more features
  • Customer friendly licensing and pricing
  • Connectors available for B2B integrations 
  • Great community support due to well known open source projects (eg: Camel, CXF, Synapse)
  • Common code base for all the components (Talend, WSO2)
  • Zero coding + custom java code and scripting support
Cons
  • Some vendors are not fully open source. Commercial version source code is proprietary.
  • Tooling support may not up to the same level as proprietary
  • Product documentation is not comprehensive as the proprietary products
Most of the advantages possessed by open source ESBs are present in WSO2 ESB. Here is a complete set of advantages you will get with WSO2 ESB.

WSO2 ESB


Pros

  • Easy to use, lightweight, lean product which requires minimal resources and easy installation
  • Open source and free. There are no separate commercial version with closed source. All the features are available in free version
  • Provides entire range of products to cover enterprise needs like ESB, Business Process Server, Analytics platform, Message Broker, Governance solution, Mobile and Security solutions which interacts smoothly
  • All the products are based on single code base built on top of a componentized architecture with common kernel (Carbon)
  • Easy to extend with custom extension points which provides the first class member privileges to custom code as internal code
  • 150+ connectors to connect with B2B applications and third party cloud APIs which are free and open source
  • Customer friendly, transparent pricing model and different levels of customer support
  • Zero coding and fully configuration based with ever increasing visual tooling based on eclipse platform. No programming skills required.
  • Cloud native implementations make it easy to move your enterprise solutions to cloud without any hazzle
  • Lot of community support from apache projects and WSO2 own community through blog posts/articles
  • Support is provided by the same engineers who develop the code and hence better response times
Cons

  • Visual tooling is not up to the proprietary solution level
  • Product documentation is not comprehensive as proprietary solutions

Labels:

Comments

  1. UnknownMarch 4, 2016 at 9:32 AM

    Hi there,

    Thank you for this information. Would you happen to know any exact dollar figures regarding WSO2 support ? I am aware that its proportional to the number of JVMs. I am having a hard time figuring out the actual amounts.

    Thanks in advance.

    ReplyDelete
  2. chanakaudayaMarch 4, 2016 at 6:21 PM

    Hi Aizaz,
    You can contact WSO2 sales team for the exact pricing. You can fill the below form with your request and they will respond you.
    http://wso2.com/contact/

    ReplyDelete
  3. Amala sir please give me access to 6, 7,8,9 classes telugu plans please sirAugust 22, 2018 at 8:47 AM

    I am not seeing any comparisons here , explaining only about wso2 not about mule esb . If you know please compare with diffrent esb's and publish

    ReplyDelete
  4. PriyaDecember 23, 2019 at 11:51 PM

    I have read your blog and I got very useful and knowledgeable information from your blog. It’s really a very nice article
    Mulesoft Online Training
    Mulesoft Training in Hyderabad

    ReplyDelete
  5. bhanu sreeeNovember 16, 2020 at 8:55 PM

    Nice Blog!!
    Workday Studio Training
    Workday Studio Online Training

    ReplyDelete
  6. bhanu sreeeDecember 14, 2020 at 10:49 PM


    This is an amazing blog, thank you so much for sharing such valuable information with us.
    Mulesoft Training in Hyderabad
    Mulesoft Training in Bangalore

    ReplyDelete
  7. bhanuFebruary 21, 2022 at 11:29 PM

    Nice Blog!!
    Mulesoft Online Training in Hyderabad
    Mulesoft Online Training in India

    ReplyDelete

Post a Comment

Popular posts from this blog

How to protect your APIs with self contained access token (JWT) using WSO2 API Manager and WSO2 Identity Server

In a typical enterprise information system, there is a high chance that people will use different types of systems built by different vendors to implement certain types of functionalities. The APIs might be hosted in an API Manager developed by vendor A and the user management can be implemented using a different vendor (vendor B). In this type of a situation, one system will not be able to directly contact the other system but they want to use both systems in tandem. Self-contained access tokens are used in these types of situations where applications can get the token from one system and use that in another system to access protected resources. In this scenario, the second system does not need to make a contact to the first system over the network to validate the user information since the token is self-contained and it has relevant details about the user. This will improve the token processing time significantly since it completely removes the network interaction. The below fig...
1 comment
Read more

WSO2 ESB creating a response for a "GET" request

When you are creating REST APIs with WSO2 ESB, you may need to send some response message back to the user when something goes wrong. In this kind of scenario, you can create a payload inside the ESB and send it back. For doing this, you can use the below configuration. <api xmlns=" http://ws.apache.org/ ns/synapse " name="LoopBackProxy" context="/loopback">    <resource methods="POST GET">       <inSequence>          <property name="NO_ENTITY_BODY" scope="axis2" action="remove"></property>          <log level="full"></log>          <payloadFactory media-type="xml">             <format>                <m:messageBeforeLoopBack xmlns:m=" http://services...
Post a Comment
Read more

WSO2 ESB usage of get-property function

What are Properties? WSO2 has a huge set of mediators but property mediator is mostly used mediator for writing any proxy service or API. Property mediator is used to store any value or xml fragment temporarily during life cycle of a thread for any service or API. We can compare “Property” mediator with “Variable” in any other traditional programming languages (Like: C, C++, Java, .Net etc). There are few properties those are used/maintained by ESB itself and on the other hand few properties can be defined by users (programmers). In other words, we can say that properties can be define in below 2 categories: ESB Defined Properties User Defined Properties. These properties can be stored/defined in different scopes, like: Transport Synapse or Default Axis2 Registry System Operation Generally, these properties are read by get-properties() function. This function can be invoked with below 2 variations. get-property(String propertyName) get-property(String scop...
Post a Comment
Read more