TrustRadius: an HG Insights company

Microsoft BizTalk Server vs. WSO2 API Platform

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    Microsoft BizTalk

    Score8 out of 10
    N/AN/AN/A

    WSO2 API Platform

    Score9.4 out of 10
    Enterprise companies (1,001+ employees)
    WSO2 API Manager makes it possible for developers to both develop and manage APIs of different types. Unlike solutions which focus only on managing API proxies, WSO2 API Manager provides tools to develop APIs by integrating different systems as well. It supports a variety of API types from REST, SOAP, GraphQL, WebSockets, WebHooks, SSEs and gRPC APIs with specialized policies and governance for each different type. Being fully open source, its architecture and extensibility…

    $0

    per month

    Pricing
    Microsoft BizTalkWSO2 API Platform
    Editions & Modules
    No answers on this topic
    No answers on this topic
    Offerings
    Pricing Offerings
    Microsoft BizTalkWSO2 API Platform
    Free Trial
    NoNo
    Free/Freemium Version
    NoYes
    Premium Consulting/Integration Services
    NoYes
    Entry-level Setup FeeNo setup feeNo setup fee
    Additional Details——
    More Pricing Information
    Features
    Microsoft BizTalkWSO2 API Platform
    API Management
    Comparison of API Management features of Microsoft BizTalk Server and WSO2 API Platform
    Feature
    Microsoft BizTalk Server
    -
    Ratings
    WSO2 API Platform
    8.8
    4 Ratings
    4% above category average
    API access control00 Ratings9.54 Ratings
    Rate limits and usage policies00 Ratings9.54 Ratings
    API usage data00 Ratings8.04 Ratings
    API user onboarding00 Ratings8.04 Ratings
    API versioning00 Ratings9.04 Ratings
    Usage billing and payments00 Ratings9.04 Ratings
    API monitoring and logging00 Ratings8.54 Ratings
    Best Alternatives
    Microsoft BizTalkWSO2 API Platform
    Small Businesses
    No answers on this topic
    Amazon API Gateway
    Score7.2 out of 10
    Medium-sized Companies
    Apache Camel
    Score7.4 out of 10
    Azure API Management
    Score9.1 out of 10
    Enterprises
    TIBCO B2B Integration Solution
    Score8 out of 10
    OCI API Management
    Score7.9 out of 10
    All AlternativesView all alternativesView all alternatives
    User Ratings
    Microsoft BizTalkWSO2 API Platform
    Likelihood to Recommend
    8.0
    (7 ratings)
    9.5
    (4 ratings)
    Likelihood to Renew
    9.0
    (1 ratings)
    -
    (0 ratings)
    Usability
    7.0
    (2 ratings)
    -
    (0 ratings)
    Support Rating
    5.0
    (3 ratings)
    -
    (0 ratings)
    Implementation Rating
    9.0
    (1 ratings)
    -
    (0 ratings)
    User Testimonials
    Microsoft BizTalkWSO2 API Platform
    Likelihood to Recommend
    Microsoft
    BizTalk is well suited as middleware. Where you wish to translate an input file into an output file and send it to some endpoint. In our case, we used it to convert and send files to SAP. In many ways, it very flexible, and you can do almost anything you want with it. In many ways, it's a better solution than your SAP XI or PI as middleware, since it's much less expensive, and allows you do interface with non-SAP systems.
    Incentivized
    Read full review
    WSO2
    It's free! No argument can win a fight with that! And it's the only reason I gave it a 5. If you have no money to spend, and a simple environment you'll have a nice product. But free does come with a price. After 5 years we're still struggling with ports, and analytics (it just won't work without any errors caused by some configuration somewhere). An API Manager should work out of the box. The only configuration expertise that any developer wants to invest in, is the configuration of API's. Not the product itself... Anyone who've seen the training material, just for installing this thing will agree that this is not the way to go. Of all the API Managers out there (we've tried 4), WSO2 is the only one were you need to know how this dragon of a java application works internally. Did I already mention the humongous amount of config files?
    Incentivized
    Read full review
    Pros
    Microsoft
    • It is very user friendly. Users can change rules during run time and change workflow.
    • Huge capacity for queueing messages. It supports all types of adapters like Oracle, Salesforce, SMTP, FTP, etc. Also users can built custom adaptors.
    • If users want to dynamically deploy their solution without any downtime, this is a perfect solution. BizTalk will be a good fit, especially for public-facing websites.
    • Well-proven in the market. I used it when developing a website for Virgin Trains, catering more than 800K user requests per day.
    • Helps in load balancing.
    Incentivized
    Read full review
    WSO2
    • Authentication based on OAuth 2.0 and HTTP Basic Authentication.
    • Rate Limiting applied at different levels like Subscriber, API, Resource and Backend.
    • Monitoring by exporting the metrics in Prometheus and traces in Jaeger.
    • Mediation to perform transformation, orchestration etc.
    Incentivized
    Read full review
    Cons
    Microsoft
    • Microsoft BizTalk is over engineered for some situtations
    • Microsoft BizTalk can be frustrating to use as it forces you to use the GUI as opposed to code
    • Microsoft BizTalk is very resource intensive to create integrations
    Incentivized
    Read full review
    WSO2
    • Better QA testing prior to releases rollout
    • Better support needed
    Incentivized
    Read full review
    Likelihood to Renew
    Microsoft
    BizTalk will always be required at this hospital.
    Incentivized
    Read full review
    WSO2
    No answers on this topic
    Usability
    Microsoft
    I gave a 7 because this product BizTalk does need time and training to get familiar with the usability and features, it is not that easy to use.
    Incentivized
    Read full review
    WSO2
    No answers on this topic
    Support Rating
    Microsoft
    BizTalk Server has been supported for more than 15 years. It is well proven in the market. Microsoft has provided excellent support with technical issues.
    Incentivized
    Read full review
    WSO2
    No answers on this topic
    Implementation Rating
    Microsoft
    Make sure you have everybody and all depts. On board during testing on test server.
    Incentivized
    Read full review
    WSO2
    No answers on this topic
    Alternatives Considered
    Microsoft
    BizTalk was selected here mainly because it is easy to integrate to a .NET application (most of them are Web Service, WCF SOAP, WCF REST and Web API) and many backend databases are Microsoft SQL Server. Another benefit is that the monitoring job is easy to set up and centralize with other .NET application monitoring jobs.
    Incentivized
    Read full review
    WSO2
    Providing better capabilities comparing the overall API lifecycle management, especially the availability of API Integration layer and a strong identity layer of their own which provides an end-to-end API ecosystem that would be advantageous in terms of a large software development initiative.
    Incentivized
    Read full review
    Return on Investment
    Microsoft
    • A positive impact has been the quicker turnaround time of a part request and that part showing up in SAP using Biztalk as middleware.
    • A somewhat negative impact has been the somewhat insufficient error logging/message capture settings that Biztalk provide. This has caused occasional delays when attempted to create parts for the business.
    • A somewhat negative impact has been the need to have a specialized developer who understands Biztalk to troubleshoot issues with the Biztalk and SAP interaction when creating parts, and when adding new fields to the parts.
    Incentivized
    Read full review
    WSO2
    • We've moved away from legacy SOAP services where nobody knew what services was used by who. WSO2 eliminated at least 90% of time spend on any service.
    • Creating API's (or actually creating the API Management layer...) is so simple that new developers can get away with it in no time. Again, real time gainer.
    • Since creating API's is so simple, developers are very fast in adopting a kind of "Domain thinking". In comparison with Azure API Manager: Azure does not demand knowledge of "how" the product works, but it's definitely more difficult to get an API up and running in Azure. And for some reason, azure does not promote clean domain driven architecture. Domain Driven architecture is the greatest time saver strategy possible. And WSO2 fits nicely in there.
    Incentivized
    Read full review
    ScreenShots