What is our primary use case?
We transfer data between systems. We are to save the data to make the communication between systems synchronous. We use Anypoint MQ for making the communication synchronous. The source integration component will place the data into Anypoint MQ, and the target company will take it from there.
How has it helped my organization?
Because our customers are moving from on-premise to cloud, it's mostly costs that have been saved and nothing else.
What is most valuable?
The most valuable feature is the messaging system.
What needs improvement?
Anypoint MQ is not a pure messaging product. There are so many solutions like this, but this is not as mature as those products. The other MQ products have the capability of reprocessing and maintaining the persistence of the data. They can handle large volumes and large messages, but Anypoint MQ doesn't have those capabilities.
It can only handle a maximum size of 10 megabytes. The other MQ products have a larger capacity. IBM MQ can handle 100 megabytes of data or even solid gigabytes. This doesn't have that capability.
This solution has a lot of gaps. It's not a pure MQ product. We have sort of exposed this product with different protocols like TCP. Also, it has to evaluate these capabilities compared to the other market products.
For how long have I used the solution?
I have been using this solution for four years. The solution is used on an iPaaS cloud provided by MuleSoft.
What do I think about the stability of the solution?
The stability of Anypoint is not as mature as other MQ products.
What do I think about the scalability of the solution?
The scalability is under the hood. It is AWS, and it is reliable. It's not user-based. It is automation-based and IT products-based. We have deployed five or six individuals using Anypoint MQ.
This is not a pure provider. It is just a tactical solution cloud. In the long run, we want to go back to square one and use other MQ products like ActiveMQ or IBM MQ because of Anypoint's limitations. For instance, it can't handle more than 10 megabytes of data, and it can't hold more than 50 persistent messages.
Deployment and maintenance are automated. There is an initial automation that is required.
How are customer service and support?
Technical support is good.
Which solution did I use previously and why did I switch?
We previously used a stable solution. We moved to this product thinking that the cost would be reduced, but things are not working as expected. We plan to go back to using the old solution.
How was the initial setup?
Initial setup was very straightforward. Deployment is a cakewalk.
What about the implementation team?
You don't need an explicit skill set for deployment. Anyone can do it.
What's my experience with pricing, setup cost, and licensing?
I can't give you a straightforward answer because sometimes it depends on the usage. If you're going to have fewer than 5 million messages, it is free of cost. If you're going to have more than 5 million messages, you will be charged $100 per month.
What other advice do I have?
I would rate this solution 6 out of 10.
We thought that this was a pure demo product. We moved from IBM to MuleSoft thinking that it would work like IBM, but that's not what happened.
My advice is to try to evaluate the product beforehand and see whether it fits your needs and requirements. Check if it covers all of your use cases. Otherwise, it won't work.
There are a lot of MQ products on the market, but this is suitable for small scale customers and not for large scale.
We haven't switched solutions yet, but the plan is to switch because of this product's limitations. It doesn't cover all the use cases.
Which deployment model are you using for this solution?
Private Cloud