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. UnknownAugust 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

WSO2 ESB tuning performance with threads

I have written several blog posts explaining the internal behavior of the ESB and the threads created inside ESB. With this post, I am talking about the effect of threads in the WSO2 ESB and how to tune up threads for optimal performance. You can refer [1] and [2] to understand the threads created within the ESB. [1] http://soatutorials.blogspot.com/2015/05/understanding-threads-created-in-wso2.html [2] http://wso2.com/library/articles/2012/03/importance-performance-wso2-esb-handles-nonobvious/ Within this blog post, I am discussing about the "worker threads" which are used for processing the data within the WSO2 ESB. There are 2 types of worker threads created when you start sending the requests to the server 1) Server Worker/Client Worker Threads 2) Mediator Worker (Synapse-Worker) Threads Server Worker/Client Worker Threads These set of threads will be used to process all the requests/responses coming to the ESB server. ServerWorker Threads will be used to pr
4 comments
Read more

How puppet works in your IT infrstructure

What is Puppet? Puppet is IT automation software that helps system administrators manage infrastructure throughout its lifecycle, from provisioning and configuration to orchestration and reporting. Using Puppet, you can easily automate repetitive tasks, quickly deploy critical applications, and proactively manage change, scaling from 10s of servers to 1000s, on-premise or in the cloud. How the puppet works? It works like this..Puppet agent is a daemon that runs on all the client servers(the servers where you require some configuration, or the servers which are going to be managed using puppet.) All the clients which are to be managed will have puppet agent installed on them, and are called nodes in puppet. Puppet Master: This machine contains all the configuration for different hosts. Puppet master will run as a daemon on this master server. Puppet Agent: This is the daemon that will run on all the servers, which are to be managed using p
7 comments
Read more

How to configure timeouts in WSO2 ESB to get rid of client timeout errors

WSO2 ESB has defined some configuration parameters which controls the timeout of a particular request which is going out of ESB. In a particular  scneario, your client sends a request to ESB, and then ESB sends a request to another endpoint to serve the request. CLIENT->WSO2 ESB->BACKEND The reason for clients getting timeout is that ESB timeout is larger than client's timeout. This can be solved by either increasing the timeout at client side or by decreasing the timeout in ESB side. In any of the case, you can control the timeout in ESB using the below properties. 1) Global timeout defined in synapse.properties (ESB_HOME\repository\conf\) file. This will decide the maximum time that a callback is waiting in the ESB for a response for a particular request. If ESB does not get any response from Back End, it will drop the message and clears out the call back. This is a global level parameter which affects all the endpoints configured in ESB. synapse.global_timeout_inte
3 comments
Read more