What is our primary use case?
We primarily use the solution for different customers.
In a real-time scenario, if you want to connect any system to any system or any application to any application or any message to any message - source to target - you can use this product. Maybe there are different applications and different legacy systems. If you want to connect one system to another system, for example, SAP to Salesforce, you can. If SAP only communicates in certain formats, Salesforce might not understand these formats. However, if I want to pass data from one to the other, I use MuleSoft as the medium to do it.
How has it helped my organization?
Many companies work via an API economy. By leveraging APIs, and thereby leveraging MuleSoft, the total cost of ownership can be reduced dramatically. It's a form of digital transformation. There's a significant reduction in operational costs and maintenance when there is seamless integration between systems. The usability could also potentially be higher.
What is most valuable?
The best part of the product is there is a DataWeave Language for transformation. We can do a transformation seamlessly using DataWeave.
Customers can make use of Runtime Fabric, an RTF environment.
The stability is pretty good.
The initial setup is straightforward.
Larger organizations are more likely to see an ROI.
Technical support is quite helpful and responsive, especially at the premium level.
What needs improvement?
One should have hands-on experience on the DataWeave. If somebody knows MuleSoft and is planning to work closely with the solution, they should be comfortable with DataWeave.
Pricing is one aspect of the solution that is troublesome. There should be a lot of improvement in general, as this is a premium product, I can say. Most of the customers like to go ahead with MuleSoft implementation, but at the end of the day what is happening is when they go ahead and see the pricing, they get scared.
Performance-wise also they need to improve a lot. Basically, the number of ports is lacking. When you have ETL kind of transformation, ideally it will be supported, however, we end up using a large number of ports. That will drastically increase the cost to the customer, however. They need to be able to allow for an increase in ports without expanding the price.
Everybody's now integrating with AI and ML kinds of features. They need to add more of these features into their offering as well.
The scalability on offer could be better.
For how long have I used the solution?
I've been using the solution for the last five years or so. It's been a while.
What do I think about the stability of the solution?
The scalability in general is good. We don't see any issues. There aren't bugs or glitches. It doesn't crash or freeze. It's very reliable.
What do I think about the scalability of the solution?
In terms of scalability capabilities, much improvement is required. That is my understanding. There should be more scalability options. As of now, a few options are there, however, from my understanding, they should come up with more and more scalability options.
Right now, what we have access to is okay. My point is mainly that they can still add more onto that.
How are customer service and technical support?
There are different levels of support, including silver, gold, and platinum. For premium customers, support is always excellent. I can't speak to silver and gold level support contracts, however, I've never known there to be a problem with the level of support any client can receive.
How was the initial setup?
The initial setup is not overly complex. It's pretty straightforward. A company shouldn't have too much trouble with the process.
What about the implementation team?
We can handle the implementation ourselves. If a company has someone who is well-versed in the solution, they can likely do their own deployment. However, there is some complexity. There needs to be a good understanding of the product and its administration. This is very important especially if you plan to deploy in a hybrid environment.
What was our ROI?
At the end of the day, if a customer is spending such an amount of money, they want to see an ROI. However, small and medium companies, due to the pricing, are less likely to witness any ROI. Enterprise-level organizations will likely see results that are much more impressive.
What's my experience with pricing, setup cost, and licensing?
It's an expensive product. They need to work on their pricing so that potential customers aren't scared off.
While enterprise-level organizations may not mind the pricing, smaller organizations wouldn't find the price suitable. Therefore, they should work to maybe develop a cheaper license for small companies so that they too can get the benefits of the solution - but at a much smaller cost.
What other advice do I have?
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.
Which deployment model are you using for this solution?