TrustRadius: an HG Insights company

Azure Service Bus vs. IBM Integration Bus

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    Azure Service Bus

    Score9.5 out of 10
    N/AMicrosoft offers Azure Service Bus as a reliable cloud messaging as a service (MaaS) and simple hybrid integration solution.N/A

    IBM Integration Bus

    Score10 out of 10
    N/AIBM Integration Bus, replacing the former WebSphere Message Broker, is used to connect applications together, regardless of the message formats or protocols that they support. This connectivity helps to ensure diverse applications can interact and exchange data with other applications in a flexible, dynamic, and extensible infrastructure.N/A
    Pricing
    Azure Service BusIBM Integration Bus
    Editions & Modules
    No answers on this topic
    No answers on this topic
    Offerings
    Pricing Offerings
    Azure Service BusIBM Integration Bus
    Free Trial
    NoNo
    Free/Freemium Version
    NoNo
    Premium Consulting/Integration Services
    NoNo
    Entry-level Setup FeeOptionalNo setup fee
    Additional Details——
    More Pricing Information
    Best Alternatives
    Azure Service BusIBM Integration Bus
    Small Businesses
    No answers on this topic
    No answers on this topic
    Medium-sized Companies
    Mule ESB
    Score8.3 out of 10
    Mule ESB
    Score8.3 out of 10
    Enterprises
    IBM DataPower Gateway
    Score9.5 out of 10
    IBM DataPower Gateway
    Score9.5 out of 10
    All AlternativesView all alternativesView all alternatives
    User Ratings
    Azure Service BusIBM Integration Bus
    Likelihood to Recommend
    8.0
    (1 ratings)
    7.0
    (1 ratings)
    User Testimonials
    Azure Service BusIBM Integration Bus
    Likelihood to Recommend
    Microsoft
    If you need a cloud-based service bus or a simple to use queue/topic/routing/pub-sub service, then Azure Service Bus is a very good choice at a reasonable price and performance. Typically on-premise we'd use RabbitMQ because it "just works", but if you're building a "cloud-first" application, then this is the one to go with. It's especially easy to integrate with if you're already embedded in the Microsoft ecosystem.
    Incentivized
    Read full review
    IBM
    Routing, protocol transformation, message transformation and service aggregation are very well performed by WebSphere Message Broker (WMB). It is not very suitable for integration with databases.
    Incentivized
    Read full review
    Pros
    Microsoft
    • Acting as a basic queuing service it works very well.
    • One of the best parts is that Azure Service Bus can work over HTTPS which helps in strict firewall situations. There is a performance hit if you choose to use HTTPS.
    • The routing capabilities are quite good when using topics and subscriptions. You can apply filters using a pseudo-SQL-like language though the correlation filters are quick and easy options.
    • Costs are very reasonable at low-ish volumes. If you're processing 10's of millions of messages a month... it may be a different story.
    Incentivized
    Read full review
    IBM
    • Graphical data mapper
    • Support for different programming languages
    • Integration with MQ
    • Support for different parsers
    Incentivized
    Read full review
    Cons
    Microsoft
    • The SqlFilter could be a little easier to use, but it's not terrible.
    • The performance while using HTTPS for the connection is a little slow compared to direct connections using AMQP ports.
    • There is a size limit to the message - unlike RMQ for instance, Azure Service Bus caps messages to 256kb on the standard tier.
    Incentivized
    Read full review
    IBM
    • Logging
    • Debugging
    • Code quality tools
    • Feature specific installation
    Incentivized
    Read full review
    Alternatives Considered
    Microsoft
    RabbitMQ is simple and awesome... but so is Azure Service Bus. Both accomplish the same thing but in different environments. If you're building a cloud-native application - especially one that is serverless by design - Azure Service Bus is the only real choice in Azure. It works well, it's performance, and it's reasonably priced in the Standard tier. From our testing, RMQ is more performant, but it's hard to compare service-based implementations vs RMQ installed on VMs.
    Incentivized
    Read full review
    IBM
    Websphere message broker supports a lot more protocols than any other similar tool.
    Incentivized
    Read full review
    Return on Investment
    Microsoft
    • Compared to open-source free software like RMQ, Azure Service Bus does have some costs to it. But the cost is reasonable.
    • Also unlike RMQ, Azure Service Bus doesn't require you to stand up any hardware - so it's very easy to use and saves time/money from that perspective.
    Incentivized
    Read full review
    IBM
    • It helped us in improving the speed to market for our services/APIs.
    • Learning curve is quite long
    Incentivized
    Read full review
    ScreenShots