TrustRadius: an HG Insights company

Save this comparison

Save this comparison

Add Product

Recommended Comparisons

    Overview
    ProductRatingMost Used ByProduct SummaryStarting Price

    Azure API Management

    Score9.1 out of 10
    N/AMicrosoft's Azure API Management supports creation of API.

    $0.04

    per 10,000 calls

    IBM MQ

    Score9 out of 10
    N/AIBM MQ (formerly WebSphere MQ and MQSeries) is messaging middleware.N/A

    RabbitMQ

    Score9.5 out of 10
    N/ARabbitMQ, an open source message broker, is part of Pivotal Software, a VMware company acquired in 2019, and supports message queue, multiple messaging protocols, and more. RabbitMQ is available open source, however VMware also offers a range of commercial services for RabbitMQ; these are available as part of the Pivotal App Suite.N/A
    Pricing
    Azure API ManagementIBM MQRabbitMQ
    Editions & Modules
    Consumption
    0.042 per 10,000 calls
    Lightweight and serverless version of API Management service, billed per execution
    Developer
    $48.04
    per month Non-production use cases and evaluations
    Basic
    $147.17
    per month Entry-level production use cases
    Standard
    $686.72
    per month Medium-volume production use cases
    Premium
    $2,795.17
    per month High-volume or enterprise production use cases
    Isolated
    TBA
    per month Enterprise production use cases requiring high degree of isolation
    No answers on this topic
    No answers on this topic
    Offerings
    Pricing Offerings
    Azure API ManagementIBM MQRabbitMQ
    Free Trial
    NoYesNo
    Free/Freemium Version
    NoYesNo
    Premium Consulting/Integration Services
    NoNoNo
    Entry-level Setup FeeNo setup feeNo setup feeNo setup fee
    Additional Details
    More Pricing Information
    Community Pulse
    Azure API ManagementIBM MQRabbitMQ
    Considered Multiple Products
    Microsoft
    No answer on this topic
    IBM
    Chose IBM MQ
    I've also used Apache Kafka and RabbitMQ. Compared to these, IBM MQ offers superior reliability and transactional integrity, making it a better choice for complex, mission-critical enterprise environments where message delivery and security are paramount. We chose IBM MQ for …
    Incentivized
    Chose IBM MQ
    IBM MQ is very stable and a proven product compared to other Messaging platforms available. Performance was better than WSO2 product and also the RabbitMQ. Though Kafka and IBM MQ is not directly comparable, Kafka is more suited for event based systems and also where there is …
    Incentivized
    Chose IBM MQ
    IBM MQ meets enterprise messaging business needs in terms of platform stability, functionality, support, and the list of APIs provided for client app integration, while Rabbit MQ is not an enterprise messaging platform but rather an open-source broker for point-to-point …
    Incentivized
    Open Source
    No answer on this topic
    Key User Insights
    Would buy again
    No answers on this topic
    100%
    Would buy again
    42 Answers
    91%
    Would buy again
    10 Answers
    Delivers good value for the price
    No answers on this topic
    98%
    Delivers good value for the price
    40 Answers
    100%
    Delivers good value for the price
    11 Answers
    Happy with the feature set
    No answers on this topic
    100%
    Happy with the feature set
    42 Answers
    91%
    Happy with the feature set
    10 Answers
    Lived up to sales and marketing promises
    No answers on this topic
    100%
    Lived up to sales and marketing promises
    32 Answers
    100%
    Lived up to sales and marketing promises
    7 Answers
    Implementation went as expected
    No answers on this topic
    100%
    Implementation went as expected
    39 Answers
    100%
    Implementation went as expected
    11 Answers
    Features
    Azure API ManagementIBM MQRabbitMQ
    API Management
    Comparison of API Management features of Azure API Management and IBM MQ and RabbitMQ
    Feature
    Azure API Management
    8.0
    4 Ratings
    5% below category average
    IBM MQ
    -
    Ratings
    RabbitMQ
    -
    Ratings
    API access control8.94 Ratings00 Ratings00 Ratings
    Rate limits and usage policies5.44 Ratings00 Ratings00 Ratings
    API usage data8.94 Ratings00 Ratings00 Ratings
    API user onboarding9.03 Ratings00 Ratings00 Ratings
    API versioning8.94 Ratings00 Ratings00 Ratings
    Usage billing and payments5.23 Ratings00 Ratings00 Ratings
    API monitoring and logging9.84 Ratings00 Ratings00 Ratings
    Best Alternatives
    Azure API ManagementIBM MQRabbitMQ
    Small Businesses
    Amazon API Gateway
    Score7.2 out of 10
    No answers on this topic
    No answers on this topic
    Medium-sized Companies
    Amazon API Gateway
    Score7.2 out of 10
    Apache Kafka
    Score8.9 out of 10
    Apache Kafka
    Score8.9 out of 10
    Enterprises
    OCI API Management
    Score7.9 out of 10
    Apache Kafka
    Score8.9 out of 10
    Apache Kafka
    Score8.9 out of 10
    All AlternativesView all alternativesView all alternativesView all alternatives
    User Ratings
    Azure API ManagementIBM MQRabbitMQ
    Likelihood to Recommend
    8.0
    (4 ratings)
    10.0
    (48 ratings)
    9.9
    (11 ratings)
    Likelihood to Renew
    -
    (0 ratings)
    9.1
    (1 ratings)
    -
    (0 ratings)
    Usability
    -
    (0 ratings)
    9.1
    (7 ratings)
    8.0
    (1 ratings)
    Availability
    -
    (0 ratings)
    9.5
    (29 ratings)
    -
    (0 ratings)
    Support Rating
    -
    (0 ratings)
    9.1
    (27 ratings)
    6.5
    (4 ratings)
    User Testimonials
    Azure API ManagementIBM MQRabbitMQ
    Likelihood to Recommend
    Microsoft
    APIM is useful for the standard scenarios:
    1) Securing your back-end APIs - If you have a legacy back-end web service that has a basic authentication scheme, you can add some additional security by placing APIM in front, and requiring subscription keys. Leverage your existing firewall to ensure only your APIM instance can communicate with your back-end API, and you've basically added a layer of protection.
    2) Lift and shift - there are always going to be clients that don't want to update their clients to use a newer API; in some cases you can make a newer API look like an older one by implementing some complex policies in APIM. You can also do the opposite, making older APIs look new, such as making an XML back-end accept both JSON and XML.
    3) Centralizing your APIs - if you've acquired another company and want to make their API set look as if it's a part of the larger whole, APIM is an easy way to provide a consistent front-end interface for developers.
    Incentivized
    Read full review
    IBM
    In the context of Internet of Things (IoT) applications, IBM MQ plays a pivotal role in managing the substantial data streams emanating from interconnected devices. Its primary function is to guarantee the dependable transmission and processing of data, catering to a diverse range of IoT use cases, including but not limited to smart city initiatives, healthcare monitoring systems, and industrial automation solutions. In the telecommunications sector, IBM MQ is employed for message routing, call detail record (CDR) processing, and network management to ensure real-time data exchange and fault tolerance. When managing the supply chain and logistics, IBM MQ is used to ensure timely and accurate communication between different entities, including suppliers, warehouses, and transportation providers. IBM MQ can be cost-prohibitive for smaller organizations due to licensing and maintenance costs. In such cases, open-source or lightweight messaging solutions may be more appropriate. For scenarios requiring extremely low-latency, real-time data exchange, and high throughput, other messaging technologies, like Apache Kafka, may be more suitable due to their specialized design for such use cases.
    Incentivized
    Read full review
    Open Source
    It is highly recommended that if you have microservices architecture and if you want to solve 2 phase commit issue, you should use RabbitMQ for communication between microservices. It is a quick and reliable mode of communication between microservices. It is also helpful if you want to implement a job and worker mechanism. You can push the jobs into RabbitMQ and that will be sent to the consumer. It is highly reliable so you won't miss any jobs and you can also implement a retry of jobs with the dead letter queue feature. It will be also helpful in time-consuming API. You can put time-consuming items into a queue so they will be processed later and your API will be quick.
    Incentivized
    Read full review
    Pros
    Microsoft
    • Easy commissioning of APIs.
    • Great policies to control access.
    • Easy mock services for testing.
    Incentivized
    Read full review
    IBM
    • The documentation is very clear,It is understandable and the support helps to configure it in the best way.
    • Server guidelines make it possible to get the most out of work management. It's broad, we can work with different operating systems, I really recommend using linux.
    • It is highly compatible with systems, brockers, applications, and data accumulation programs, it is possible to configure everything so that after the installation of programs, they can communicate with each other and then throw data to an external program that accumulates it and represents in clear details of steps to follow and make business decisions.
    Incentivized
    Read full review
    Open Source
    • What RabbitMQ does well is what it's advertised to do. It is good at providing lots of high volume, high availability queue. We've seen it handle upwards of 10 million messages in its queues, spread out over 200 queues before its publish/consume rates dipped. So yeah, it can definitely handle a lot of messages and a lot of queues. Depending on the size of the machine RabbitMQ is running on, I'm sure it can handle more.
    • Decent number of plugins! Want a plugin that gives you an interface to view all the queues and see their publish/consume rates? Yes, there's one for that. Want a plugin to "shovel" messages from one queue to another in an emergency? Check. Want a plugin that does extra logging for all the messages received? Got you covered!
    • Lots of configuration possibilities. We've tuned over 100 settings over the past year to get the performance and reliability just right. This could be a downside though--it's pretty confusing and some settings were hard to understand.
    Incentivized
    Read full review
    Cons
    Microsoft
    • Lack of robustness is a bit of an issue. Several other providers offer more options and capabilities, but then, they are lacking in interface ease.
    • As with anything Azure, pricing is really hard to stay on top of. I always find that you really don’t know what you’re paying for until you get the bill. Having an excellent Azure Administrator can help resolve that.
    • Integrating with app services outside of Azure can be a challenge, or at least much more challenging than just using Azure App Services.
    Incentivized
    Read full review
    IBM
    • There is limitation on number of svrconn connections you can have to MQ on the mainframe which has been an major issue for us. This has been an issue for us for over 4 years and still no fix although I am aware IBM have been working on a solution over the last year.
    • When upgrading to MQ V9.3 on our MQ appliances there is no fall-back option. This was the same for MQ V9.2 upgrade from MQ V9.0. For production upgrades this I believe is not acceptable.
    • AMS is not supplied as part of the standard mainframe MQ licence. You need an extra licence. IBM tell customers how important security and protecting data is yet they still want to charge for this software. The cost of MQ on the mainframe is not cheap so I would expect AMS to be part of the base product.
    Incentivized
    Read full review
    Open Source
    • It breaks communication if we don't acknowledge early. In some cases our work items are time consuming that will take a time and in that scenario we are getting errors that RabbitMQ broke the channel. It will be good if RabbitMQ provides two acknowledgements, one is for that it has been received at client side and second ack is client is completed the processing part.
    Incentivized
    Read full review
    Usability
    Microsoft
    No answers on this topic
    IBM
    I give it a nine because it has significantly improved my team's data reliability and operational efficiency. Its great security features give us peace of mind, knowing our sensitive data is well protected. While the setup might initially be complex, I believe the long-term benefits far outweigh this hurdle.
    Incentivized
    Read full review
    Open Source
    RabbitMQ is very easy to configure for all supported languages (Python, Java, etc.). I have personally used it on Raspberry Pi devices via a Flask Python API as well as in Java applications. I was able to learn it quickly and now have full mastery of it. I highly recommend it for any IoT project.
    Incentivized
    Read full review
    Reliability and Availability
    Microsoft
    No answers on this topic
    IBM
    The messages are delivered instantly with this software and it integrates with our technology stack, in terms of availability we only had one failure when we were doing some testing and integration with third parties, the features of this software make it always available and its deployment is easy for the company, it does not generate expenses due to failures
    Incentivized
    Read full review
    Open Source
    No answers on this topic
    Support Rating
    Microsoft
    No answers on this topic
    IBM
    There are very specific things that must be elevated to more specialized areas of support, but the common support is very agile when receiving questions or when we leave concerns in real time. I recommend the support of the program in this regard.
    Incentivized
    Read full review
    Open Source
    I gave it a 10 but we do not have a support contract with any company for RabbitMQ so there is no official support in that regard. However, there is a community and questions asked on StackOverflow or any other major question and answer site will usually get a response.
    Incentivized
    Read full review
    Alternatives Considered
    Microsoft
    Azure APIM vs Amazon API Gateway:
    1) Azure APIM was a complete package that included a developer portal.
    2) We are very Microsoft centric - so the Microsoft product suite aligned very well with our business needs.
    3) It was faster and easier to stand up Azure APIM for testing than it was for the Amazon API Gateway.
    Incentivized
    Read full review
    IBM
    We found IBM MQ very easy to get started and quick to learn by the new users with a short learning curve and seamlessly integrates with IBM products, and quick to perform self-service analytics and make informed business decisions. IBM MQ is also very straightforward in creating simple and best reports, which are very profitable and productive.
    Incentivized
    Read full review
    Open Source
    RabbitMQ has a few advantages over Azure Service Bus 1) RMQ handles substantially larger files - ASB tops out at 100MB, we use RabbitMQfor files over 200MB 2) RabbitMQ can be easily setup on prem - Azure Service Bus is cloud only 3) RabbitMQ exchanges are easier to configure over ASB subscriptions ASB has a few advantages too 1) Cloud based - just a few mouse clicks and you're up and running
    Incentivized
    Read full review
    Return on Investment
    Microsoft
    • We can always think of positive ROI impact on business
    • It helps to easily facilitate the design, deployment, and maintenance of our APIs
    Read full review
    IBM
    • Positive- Message Reliability and Reduced downtime, increases the ROI many times.
    • Positive- Increased stability and enhanced customer experience
    • Negative- cost is very high - Both licensing and integration cost
    • Negative- Learning and training cost of IBM MQ is high as its complex to use and integrate
    Incentivized
    Read full review
    Open Source
    • Positive: we don't need to keep way too many backend machines around to deal with bursts because RabbitMQ can absorb and buffer bursts long enough to let an understaffed set of backend services to catch up on processing. Hard to put a number to it but we probably save $5k a month having fewer machines around.
    • Negative: we've got many angry customers due to queues suddenly disappearing and dropping our messages when we try to publish to them afterward. Ideally, RabbitMQ should warn the user when queues expire due to inactivity but it doesn't, and due to our own bugs we've lost a lot of customer data as a result.
    • Positive: makes decoupling the web and API services from the deeper backend services easier by providing queues as an interface. This allowed us to split up our teams and have them develop independently of each other, speeding up software development.
    Incentivized
    Read full review
    ScreenShots