The Anypoint Platform developed by MuleSoft and acquired by Salesforce in early 2018 is designed to
connect apps, data, and devices anywhere, on-premises or in the cloud. This platform was built to
offer out-of-the-box connectors as well as tools that architects and developers can adopt quickly to
design, build and manage the entire lifecycle of their APIs, applications, and products.
N/A
RabbitMQ
Score 7.8 out of 10
N/A
RabbitMQ, 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
MuleSoft Anypoint Platform
RabbitMQ
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Anypoint Platform
RabbitMQ
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
MuleSoft Anypoint Platform
RabbitMQ
Considered Both Products
Anypoint Platform
Verified User
Anonymous
Chose Anypoint Platform
AWS is a very good tool but still evolving and offers a small set of API management features. The main reason why we chose MuleSoft Anypoint Platform API Manager is because it is well suited with the APIs developed in Mule ESB.
Once we have moved all of our system integration APIs to the MuleSoft Anypoint Platform, we will need to communicate with a wide variety of external systems. All of our business and service logic is stored in the aforementioned core systems. Anypoint Platform (and all of our …
Overall a better experience in pricing negotiation with the Sales team. The breadth of services offered by Mulesoft was really important and the expertise offered by our consulting partner influenced the decision. The overall deployment was completed well within the timelines. …
Once we use [MuleSoft] Anypoint Platform to host all our system integration APIS, we need to exchange data with a lot of different resources. Those listed systems are our main systems that hold all business and logic behind our service. The integration from Anypoint Platform …
We selected Mulesoft for speed of implementation. We did not have the luxury of time and needed a solution that can be learned and implemented within weeks so we can take advantage of newly formed partnerships. The training that was provided to use during our pre-sales and …
We believe Anypoint Platform is best in breed and has features that match nearly any other iPaaS offering. It also allows for accomplishing much more challenging and complex integrations due to the ability to connect to nearly any system, use custom connectors, and embed …
The main problem with this software is the different connector type that is used for different protocols except for a different SAP connector. There is only one connector called SAP. It will be great if there will have a different connectors like idoc, RFC, proxy, etc.
Anypoint has tons of capabilities baked in one platform, and other competitors like Built.io or Workato may not have all those like Anypoint Exchange. However where these products shine are in usability, as it's ridiculously easy to build integrations using Built.io. I was …
Anypoint Platform is really very easy to adopt for application integration. Simple UI and easy data weave language allows user to focus on business portion only. The API management and deployment of application are hassle free. We have selected Anypoint platform because it is …
Dell Boomi is kind of similar in drag and drop implementation. However, it doesn't have as many connectors (shapes in Dell Boomi). Moreover, it also doesn't have deployment stuff on its own.
Informatica is way behind Dell Boomi and Anypoint Platform, but users are still using it …
Compared to Dell Boomi the API management suite of Mulesoft is much mature, however if its only about the integration , then i would always go for Dell Boomi, as there is no infrastructure setup that needs to be done from the developer's end.
The main reason why we chose Anypoint API Manager is because it is well suited with the APIs developed in Mule ESB. AWS, on the other hand, is a very good tool but still evolving and offers a small set of API management features.
API led architecture focus with a decent API ecosystem for developer collaboration, policy management and declarative implementation. Batch processing, visualization, Anypoint MQ and ObjectStore leave a lot to be explored. Multiple deployment models make it worth considering.
It enables customers to expose their APIs in a very simple and fast way. It can be used by non-expert developers. It is compliant with all major connection and data representation world standard.
We provide options to customers to choose from the best tools. Customers are the decision makers. Personally, because of open-source and large community base, MuleSoft is the repo in the market.
It is a powerful tool with smart intelligence. The drag and drop feature makes my work easy. The tool has great connecting support which is the best reason to use the tool on a daily basis. Powerful functionality with designing and implementing APIs. Hosted on public IP.
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
It is very easy to use as it has a simple function to connect and use RabbitMQ. It is having Fast Learning curve, Any newbies can learn it in a week or month. It is having proper documentation, we are able to find all the details about its functionality and usage of it. The …
I have not used other products other than a roll-your-own solution. The Selection of RabbitMQ was made before I began working on the project but I was able to leverage it well without making major changes to the existing apps. This was particularly helpful in lowering risks. I …
For basic use cases, SQS is way easy to deploy and maintain compared to RabbitMQ. RabbitMQ can cover a lot more use-cases but actually, we did not face specific scenarios that make it necessary to come back to RabbitMQ.
It is just better documented and seems a better fit given that is done using erlang. PubSub+ low level approach seems unsafe. They work with custom hardware whereas Pivotal RabbitMQ seem a better fit for generic hardware (cloud).
Honestly, though we're still trying out Kafka and Pulsar, I'd go with them for message broker and as traffic buffers. We are only still using RabbitMQ because it's hard to transition off after writing tons of code custom-built for RabbitMQ. Kafka is better because it's way more …
None of the options in the list are really similar products. We use Apache Camel in conjunction with RabbitMQ and we also use Oracle Integration Cloud and WSO2 for messaging. Integration Cloud is SaaS-based and low code, so it's drastically different in that regard. WS02 is …
MuleSoft Anypoint Platform is best tool in the market for developing APIs with complex structures communicating with various different types of applications including web applications as well as legacy applications. Also applications including database connectivity for fetching and updating data in the DB tables. I cant think of any scenario which MuleSoft Anypoint Platform could not be used for developing the integrations.
If you are looking for a message broker, RabbitMQ is pretty good. Its API lets you create tons of queues on demand and publish to all of them at once, while you can have 10+ consumers on each queue. It also does a good job of absorbing bursts of traffic. We've seen our queues get backed up to 3 million messages with no problem. In the modern era of GDPR, you may run into problems with keeping messages encrypted out of the box in-flight and at-rest with RabbitMQ. Not saying it's impossible, but it's tough to set up and you have to pay a high overload.
Provides wide range of popular connectors like salesforce, netsuite, sftp and many more. A user can easily integrate with those services using specific connector.
Support API development using RAML and desing tool. The platform is very good in data type classification.
Cloud deployment and post deployment monitoring is easy. A user can configure application worker as per need. Alert and notifications are real time.
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.
Has more features than what we really need so we're paying for more than we use. Sort of like paying for an Abrams tank when all we really need is a Toyota Corolla.
Not a value product, tends to be expensive.
Takes a while for developers to learn to use Mulesoft Anypoint.
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.
MuleSoft Anypoint Platform is really very easy to adopt for application integration. Simple UI and easy data weave language allows user to focus on business portion only. The API management and deployment of application are hassle free.
RabbitMQ is very usable if you are a programmer or DevOps engineer. You can setup and configure a messaging system without any programmatic knowledge either through an admin console plugin or through a command-line interface. It's very easy to spin up additional consumers when volume is heavy and it's very easy to manage those consumers either through automated scripting or through their admin console. Because it's language agnostic it integrates with any system supporting AMQP.
Anypoint Platform support is very responsive. There is also a huge knowledge base and an active online forum where answers to most questions can be found. When needed support engages the engineering group so adequate solutions or workarounds are always provided.
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.
Once we have moved all of our system integration APIs to the MuleSoft Anypoint Platform, we will need to communicate with a wide variety of external systems. All of our business and service logic is stored in the aforementioned core systems. Anypoint Platform (and all of our APIs) makes it easy to connect to various other platforms. In order to link to these many other systems, connectors and/or components are utilized, and they are simple to configure and integrate.
It is very easy to use as it has a simple function to connect and use RabbitMQ. It is having Fast Learning curve, Any newbies can learn it in a week or month. It is having proper documentation, we are able to find all the details about its functionality and usage of it. The Features of RabbitMQ are providing are matching with our business requirements.
Earlier we had a problem with missing work items with our own implementation but later using RabbitMQ is solved a problem. Now our job processing mechanism is highly reliable.
We also had a problem with scaling, processing 1k work items per second. RabbitMQ helped us to scale well with increasing work items.