If you were talking to someone whose organization is considering Mule Anypoint Platform, what would you say?
How would you rate it and why? Any other tips or advice?
I architected solutions using Oracle SOA/OSB, Spring Boot, MuleSoft Anypoint Platform on cloud / on-premises and hybrid modes;
What I see is though if you are an enterprise and have enough money then they can opt for Mule; All the enterprise level connectors like SAP etc. even connectors like FTPS are also charged additionally. Also you have multiple enterprise support models like Gold, Platinum and Titanium.
Another issue with Mule is it's complex licensing model and unclear/in complete documentation. Like for example in case of Mongo DB there is no way you can understand the significance of "connection string" based connectivity like LDAP based Authentication or X509 kind of connectivity.
Mule has Community Addition which is like Open Source but there are very few connectors to work with like HTTP, Database (Standard RDBMS), File, FTP etc.. But there's no support. Community support I frankly didn't see much neither the open-source cameraderie.
At the same time, I see MuleSoft as a Platform which can propel / transform any legacy enterprise into digital age.
Following are the reasons.
1. Mule comes with 100s of connectors for Communication protocols (HTTP, TCP, WebSockets, FTP, with Security etc..) + Data Protocols (Database, File, SAP, Salesforce) etc.. and supports a wide range of data formats like JSON / XML / CSV etc.
2. Mule Advocates API Led connectivity dividing the application into Data/System APIs (Abstracting Data Layer), Process APIs (A mash-up of System APIs), Experience APIs (supporting different UI Channels like Web, Mobile etc.) on top of Process APIs
3. It gives components a low code platform, with data transformation from one form to another form, Batch and other standard integration patterns like Routers/aggregators / scatter-gather etc.
The toolset and separation of concerns at each layer give a great level of flexibility for transforming any legacy enterprise into the digital age.If you are an SMB or you have good developer workforce and you have standard integration scenarios like, File, FTP, Batch, Database or even otherwise -- you should look towards Spring Integration. You have great community and widely available documentation. Spring has other options for support as well as deploying to cloud to either VMware or as part of AWS Elastic Beanstalk.
I'd rate the solution at an eight out of ten. We've mostly been very happy with the product's capabilities so far.
We work with our customers on integrating the solution. We aren't MuleSoft partners, nor are we direct end-users. The solution works across multiple deployment models, including on-premises and hybrid cloud. They also have their own managed cloud, which is the preferred method. I'd rate the solution at an eight out of ten. If a company is interested in implementing the solution, first of all, they need to be clear with the requirements. They need to understand what exactly they were doing in terms of integration and they need to see what the current challenges are that they were facing. It's a good idea to analyze the different products which are available in the market. When a comparison is done, they are more likely to choose something that best fits their needs. A customer should never compromise on the quality of the product or the capabilities. If they plan to invest, they should do so by investing in a solution that has the best possible features for their budget.
I would rate Mule Anypoint Platform an eight out of ten.
I would rate this solution an eight out of ten.
We're just a customer. We don't have a business relationship with the company. I'm not sure of which version of the solution we are using right now. I'd recommend this solution to others. However, I'd advise that they be careful of the licensing terms. They're so convoluted. There are many hidden costs in the use of the product and you may not realize what it will actually cost until it's too late. Overall, I would rate the solution at a seven out of ten.
We work on all three models, that is, cloud, on-premises, and RTF. Nowadays, people are going for cloud solutions. The cloud model is good if you do not have any compliance issues for storing customer information on the cloud. However, if you have compliance issues, you can go for on-premises deployment. There is also RTF deployment, which is a new and very stable option. People who have used the RTF option found it to be very good. I would recommend this solution. I would rate Mule Anypoint Platform a nine out of ten.
I would rate this solution an eight out of 10.
The pricing is a bit high for clients. As a developer, and my superiors and architects agree, that this is the easiest tool to use. I've worked with two configuration technologies, one was open-source and there is a huge difference with this. This is the easiest and best tool available. Mule should consider lowering the price. The should make improvements for B2B enterprises I would rate it an eight out of ten as it's a very good product.
I would advise anyone interested that you need to make sure you're using the right patents. I think that's important. On a scale of one to ten, I would rate Mule Anypoint Platform an eight.
My advice for anyone considering this as a solution is first to get to understand exactly what resources will be needed from an architecture perspective. It is important to know how the MuleSoft Anypoint Platform works, what are the limitations, and the kind of consumption gradient they need. The idea would be to acquire enough resources — not too much that you overspend for nothing and not too low that there are performance or other problems. That was actually one of the good things about MuleSoft when we started to do our discovery or due diligence. In the presale process, a presale engineer explained some technical perspective on the MuleSoft solution and we were able to plan and handle it accordingly. They explained how their runtime how it works and what the provisions were. We had to decide how many cores we needed to get. They might delve into areas where we needed any additional explanation as to what they meant. They were very, very helpful because they assisted us in understanding instead of making anyone feel bad or have a difficult deployment because it was not so straightforward a process. They helped us to understand it and when you understand it, it becomes very easy from a planning perspective. On a scale from one to ten, one being the worst and ten being the best. I would rate this product about an eight. It is not a ten because of the problem with the connectors and right now the pricing models. Sometimes with pricing, you need to understand what you understand and when you need to be careful. The pricing may not be good or bad I don't know. In our case, it is what it is and we are satisfied. The thing that I saw was that other people who are dealing with MuleSoft, who don't have such a great relationship and perfect support team, might have misunderstood the pricing model. Because of that, the customer did not know what exactly they need to get and how the product filled their needs. So MuleSoft needs to keep their level of client education up to the level they did for us. Another thing with education has to do with training. There's not too much material on the MuleSoft cloud platform around anywhere. This is probably because at this point they have to do it by themselves because there is not a big community of users. It is very rare to find something on MuleSoft easily if you have an issue. You always can find information on Google and sometimes you can solve your issues. But what I am talking about is something a little bit more organized as clusters of information and videos. I wish I could get information from dedicated community platforms. It is maybe not something that they feel they can address, but maybe they actually can. Maybe they can create some kind of relationship with information and training platforms to introduce some awareness of their product.
We use the public cloud deployment model. We used to use the on-premises model, but we moved over to the cloud. I would advise others considering using the solution to do some kind of small project to start. Then, when you scale to a more production-like architecture, that's when you need the support and help. If you don't have it there in-house, you need to find that support. All of those tricky details which you maybe didn't do in that first phase, you need to do, and proper support will help. Make sure you have it. I would rate the solution eight out of ten. I'd rate it higher, but we got into some technical setups where we needed more expertise. We had to wait for that expertise. We got it, finally, through consultants, but we expected to get it more from the company. All they could do for us was point us in the direction of where we could get help.
It is a very good ESB tool for integration. It is easy to learn and their documentation is very well organized.
How do you or your organization use this solution?
Please share with us so that your peers can learn from your experiences.
Let the community know what you think. Share your opinions now!