CTO and Head of Strategy, Technology & Innovation at Cashapona
Real User
Top 5
2024-04-29T07:56:00Z
Apr 29, 2024
Working with Mule ESB has taught us the value of experience with different ESBs, making it easier to adapt to new solutions. Overall, I would rate the solution a ten out of ten.
System Analyst / Senior Software Engineer at a tech services company with 1-10 employees
Real User
Top 10
2024-02-26T11:44:00Z
Feb 26, 2024
We were using the solution for the transformation of requests. So, it was good for us to exchange data and establish communication between different legacy and modern systems. Mainly, we were using the transformers. Other than that, the process flows were very helpful for us to implement them. Earlier, the integration was done into the development and through the languages itself, like custom implementation. With Mule ESB, we could do many transformations and implement the process flows within the services itself. We were having the same service which we had to distribute among the different clients. The proxy and role assignment was done through Mule ESB. This helped us with the distribution of services among different vendors and then validating them based on their roles. Although we faced some challenges initially, we got the expertise by learning from Mule ESB itself. Eventually, everything got smooth, and we never had any issues with the deployment. Depending on the requirements and the size of the projects, I would recommend Mule ESB to other users. Overall, I rate the solution a seven out of ten.
Readiness Manager/Business Analytics for GCC India Operations at Ericsson
Real User
Top 5
2024-02-12T10:34:05Z
Feb 12, 2024
Mule ESB supported our organization with its archiving capabilities, like the way we used to receive support from webMethods.io. My company used to raise tickets with the support team if we faced any issues with the product. If the product's support team were able to resolve our issues with the tool, they would send our company emails with complete solutions to our issues. The support team also used to try to fix our company's issues with the product through share screen options. I only use the product's API part, and I haven't seen any issues with the product. Owing to the aforementioned reasons, I can't comment on the product's features that I find to be most effective for our company's integration needs. I like the development part of the product. I can't comment on the stability of the product since I used to use it in the environment as it does not move to the cloud. The development was not that easy in Mule ESB compared to webMethods.io, which offers a flow service. I would recommend webMethods.io to others since I have a good understanding and knowledge of the tool. If people still insist on looking for other products, I need to involve another person who can provide them with the right judgment. Maybe someone who has worked on both of the products simultaneously can be an intelligent person. If you ask my individual opinion, I would go with webMethods.io. Mule ESB is more inclined towards Java codes. If you are a new user who knows about Java, then Mule ESB will be easy for you to use. With webMethods.io, you can use it even without knowing any coding language. Considering the aforementioned comparison, I feel that webMethods.io is better than Mule ESB. I rate the overall tool a six out of ten.
I would rate this solution seven out of ten. I would recommend this solution for those who want to use it. It will depend on the customer's needs and what they want to use it for.
To those looking into implementing this solution, I would say that you will enjoy the experience of using Mule. I would rate this solution as a ten out of ten.
Nine out of 10. It's one of the better open-source tools for development. It provides seamless support and transition. I give it a high rating because most organizations are using MuleSoft. IBM and Oracle are also in the middleware market. MuleSoft is open-source and readily available, so people can meet their needs easily with this tool. We have a REST API with minimal integration and configuration, so we can easily use this solution.
Vice President at a philanthropy with 1-10 employees
Real User
2022-01-12T21:36:27Z
Jan 12, 2022
They have a package to get you started. I would advise using at least a partner at the very beginning so that they can show you the best practices within MuleSoft and different layers of APIs. Sometimes, there are challenges around security and things like that. So, my advice is to get external help to get your developers started on it. Once they're taught the best practices, your intermediate to senior developers will pick it fairly quickly. I would rate it a nine out of 10.
I rate Mule ESB nine out of 10. It works well for me. If you're using Mule ESB for the first time, I recommend taking advantage of the free training. If you go through that training, you'll have a basic understanding of the technology. That's a good starting point.
We are thinking about moving away from Mule ESB and using Red Hat because of the high costs of Mule ESB. However, Mule ESB is a good solution. We propose Mule ESB in terms of solutions for any kind of enterprise service bus application. I rate Mule ESB a nine out of ten.
I recommend this solution to others. If you have any data exchanges with other systems, Mule ESB is very useful and easy to use, even if it's the commercial version. I rate Mule ESB a nine out of ten.
It’s a pretty good tool to have it when you try to go with a microservices type of an architecture where you want to decouple your systems and where you want all the systems to talk to each other, share that knowledge, and create those experiences that you want as part of your digital transformation journey. This tool perfectly fits that. It's a good tool to have as part of your digital transformation journey. I would rate it a seven out of ten.
Senior Software Engineer at a computer software company with 5,001-10,000 employees
Real User
2021-12-21T10:50:00Z
Dec 21, 2021
I would recommend this solution to others. It is the best integration platform for those who are looking to implement or are going for API-based architecture and microservices-based architecture. I would rate it a nine out of 10.
Senior Software Engineer at a tech services company with 10,001+ employees
Real User
2021-07-12T18:55:00Z
Jul 12, 2021
As with our other applications, MuleSoft is on-premises, but we make use of a hybrid strategy involving the use of an endpoint cloud and agent. While our initial deployment was on-premises, our control plane is on endpoint in the cloud. I am a MuleSoft developer and am working for a client. The company which I work for is a partner with MuleSoft. I would recommend MuleSoft to others. While what we are using for our current project is more than sufficient, it would be nice to see Microgateway added as a feature. I rate the solution as an eight out of ten.
Senior Consultant at a tech services company with 1-10 employees
Consultant
2020-10-19T09:33:00Z
Oct 19, 2020
I would definitely recommend Mule ESB for others to evaluate when they are choosing a product. On a scale of one to ten, I would definitely rate Mule ESB an eight. For it to be a higher rating they would need to improve the recording logs and encoding feature.
Consultant, Architecture and Standards at a tech services company with 51-200 employees
Consultant
2020-08-30T08:33:32Z
Aug 30, 2020
It's definitely allowed us to develop everything but we are stuck in testing. It works then it stops working, and now we are trying to figure out why. It's not related to the software but related to the teams that work with it. It's a new technology for us. I am still trying to discover the benefits. I know that it has many connectors, that it's a tool to integrate with Salesforce. That's when they say we cannot do what we need to without MuleSoft. We didn't use it for that purpose. For our purposes, custom integration as ESB, we are still trying to discover where our benefits are. I don't have a good idea yet. We were able to develop what we were planning to. It's highly configurable. We were able to configure the workflows and orchestrations, but we are not able to run it yet. I don't want to give people the wrong impression because of my experience so far because it may not be an accurate one. It may not be the fault of the solution. When I worked with IBM in the past, it was easier. Due to the complexities, I would rate MuleSoft a six out of ten.
We're partners of MuleSoft. We provide the solution's service to our clients. The solution would be useful for large organizations. If there are more than three or four systems, and if there is an expansion, it would work best. Small or medium enterprises with two or three systems, may find the solution a little bit unorganized. I'd rate the solution seven out of ten. If the stability were more reliable, I'd rate it higher.
IT Consultant at a financial services firm with 5,001-10,000 employees
Real User
2019-06-19T05:02:00Z
Jun 19, 2019
My opinion is that Mule ESB depends on the business and the continuity of their enrollment. If you are a system that has not much left to repair, then your products and your APIs are assets within your organization. Here in the bank, we are facing different kinds of issues when we are integrating different systems: * We are communicating with different card carriers like Mastercard and Visa. * Their standards are different according to the client requirements, i.e. exactly what kind of card they're looking for. * They can get the products according to their requirements as well as their budget. I would rate Mule ESB with 7.5 or 8 out of 10. * It's really easy to implement. * It's supporting our platforms: Windows, Linux, and Mac. * The performance. * It's free. I'm looking for an API platform that supports the whole technology as well as the next-gen. Mule ESB is lacking for self-support, self-training, and documentation. The documentation of the product is less because they're selling the training. You have to enroll for the training, then you'll get the full documentation. If you're an advanced user, you will not get much information from the public documentation.
My advice to others who are implementing this solution is to first become acquainted with the forums. There are always reports coming out about the software, and new technologies. The next thing is that I would suggest always starting with the latest version. Older versions are available, but you should install the most recent one. I would rate this solution an eight out of ten.
Developer JAVA/JEE, Mule ESB at a computer software company with 11-50 employees
Real User
2019-05-28T07:45:00Z
May 28, 2019
I will soon be migrating to version 4 of Mule ESB, although we are also interested in the WSO2 solution because it seems to be very complete. Using Mule ESB does not require somebody to be a Java developer, although there are some Java concepts that you need to know. For example, some people use JSON, and I find that they are scared of Mule ESB because it is based on Java. But really, it isn't a problem if they don't know it. This solution has good performance and support, but not everybody can use it because many of the features are expensive. Especially for application management, it is expensive compared to solutions such as WSO2. It is limiting for small and medium-sized companies. I would rate this solution a seven out of ten.
For companies looking to modernize and unlock the value of existing on-premises systems and applications, an enterprise service bus (ESB) architecture serves as a critical foundation layer for SOA. When deployed as an ESB, the Mule runtime engine of Anypoint Platform combines the power of data and application integration across legacy systems and SaaS applications, with a seamless path to the other capabilities of Anypoint Platform and the full power of API-led connectivity.
I recommend the tool for enterprises. I rate it an eight out of ten.
Working with Mule ESB has taught us the value of experience with different ESBs, making it easier to adapt to new solutions. Overall, I would rate the solution a ten out of ten.
We were using the solution for the transformation of requests. So, it was good for us to exchange data and establish communication between different legacy and modern systems. Mainly, we were using the transformers. Other than that, the process flows were very helpful for us to implement them. Earlier, the integration was done into the development and through the languages itself, like custom implementation. With Mule ESB, we could do many transformations and implement the process flows within the services itself. We were having the same service which we had to distribute among the different clients. The proxy and role assignment was done through Mule ESB. This helped us with the distribution of services among different vendors and then validating them based on their roles. Although we faced some challenges initially, we got the expertise by learning from Mule ESB itself. Eventually, everything got smooth, and we never had any issues with the deployment. Depending on the requirements and the size of the projects, I would recommend Mule ESB to other users. Overall, I rate the solution a seven out of ten.
Mule ESB supported our organization with its archiving capabilities, like the way we used to receive support from webMethods.io. My company used to raise tickets with the support team if we faced any issues with the product. If the product's support team were able to resolve our issues with the tool, they would send our company emails with complete solutions to our issues. The support team also used to try to fix our company's issues with the product through share screen options. I only use the product's API part, and I haven't seen any issues with the product. Owing to the aforementioned reasons, I can't comment on the product's features that I find to be most effective for our company's integration needs. I like the development part of the product. I can't comment on the stability of the product since I used to use it in the environment as it does not move to the cloud. The development was not that easy in Mule ESB compared to webMethods.io, which offers a flow service. I would recommend webMethods.io to others since I have a good understanding and knowledge of the tool. If people still insist on looking for other products, I need to involve another person who can provide them with the right judgment. Maybe someone who has worked on both of the products simultaneously can be an intelligent person. If you ask my individual opinion, I would go with webMethods.io. Mule ESB is more inclined towards Java codes. If you are a new user who knows about Java, then Mule ESB will be easy for you to use. With webMethods.io, you can use it even without knowing any coding language. Considering the aforementioned comparison, I feel that webMethods.io is better than Mule ESB. I rate the overall tool a six out of ten.
Overall, I would rate the solution an eight out of ten.
I would rate the solution an eight out of ten. The solution is a good and stable product with great community support.
On a scale from one to ten, I would give Mule ESB an eight.
I rate the solution a nine out of ten.
I would rate this solution seven out of ten. I would recommend this solution for those who want to use it. It will depend on the customer's needs and what they want to use it for.
I rate this solution eight out of 10.
To those looking into implementing this solution, I would say that you will enjoy the experience of using Mule. I would rate this solution as a ten out of ten.
Nine out of 10. It's one of the better open-source tools for development. It provides seamless support and transition. I give it a high rating because most organizations are using MuleSoft. IBM and Oracle are also in the middleware market. MuleSoft is open-source and readily available, so people can meet their needs easily with this tool. We have a REST API with minimal integration and configuration, so we can easily use this solution.
They have a package to get you started. I would advise using at least a partner at the very beginning so that they can show you the best practices within MuleSoft and different layers of APIs. Sometimes, there are challenges around security and things like that. So, my advice is to get external help to get your developers started on it. Once they're taught the best practices, your intermediate to senior developers will pick it fairly quickly. I would rate it a nine out of 10.
I would give this product a rating of ten out of ten.
I rate Mule ESB nine out of 10. It works well for me. If you're using Mule ESB for the first time, I recommend taking advantage of the free training. If you go through that training, you'll have a basic understanding of the technology. That's a good starting point.
We are thinking about moving away from Mule ESB and using Red Hat because of the high costs of Mule ESB. However, Mule ESB is a good solution. We propose Mule ESB in terms of solutions for any kind of enterprise service bus application. I rate Mule ESB a nine out of ten.
I recommend this solution to others. If you have any data exchanges with other systems, Mule ESB is very useful and easy to use, even if it's the commercial version. I rate Mule ESB a nine out of ten.
On a scale from one to ten, I would give Mule ESB an eight.
It’s a pretty good tool to have it when you try to go with a microservices type of an architecture where you want to decouple your systems and where you want all the systems to talk to each other, share that knowledge, and create those experiences that you want as part of your digital transformation journey. This tool perfectly fits that. It's a good tool to have as part of your digital transformation journey. I would rate it a seven out of ten.
I would recommend this solution to others. It is the best integration platform for those who are looking to implement or are going for API-based architecture and microservices-based architecture. I would rate it a nine out of 10.
I rate the solution nine out of 10.
As with our other applications, MuleSoft is on-premises, but we make use of a hybrid strategy involving the use of an endpoint cloud and agent. While our initial deployment was on-premises, our control plane is on endpoint in the cloud. I am a MuleSoft developer and am working for a client. The company which I work for is a partner with MuleSoft. I would recommend MuleSoft to others. While what we are using for our current project is more than sufficient, it would be nice to see Microgateway added as a feature. I rate the solution as an eight out of ten.
I rate Mule ESB a nine out of ten.
I would definitely recommend Mule ESB for others to evaluate when they are choosing a product. On a scale of one to ten, I would definitely rate Mule ESB an eight. For it to be a higher rating they would need to improve the recording logs and encoding feature.
I would rate this solution a six out of ten.
I would rate this solution an eight out of ten.
It's definitely allowed us to develop everything but we are stuck in testing. It works then it stops working, and now we are trying to figure out why. It's not related to the software but related to the teams that work with it. It's a new technology for us. I am still trying to discover the benefits. I know that it has many connectors, that it's a tool to integrate with Salesforce. That's when they say we cannot do what we need to without MuleSoft. We didn't use it for that purpose. For our purposes, custom integration as ESB, we are still trying to discover where our benefits are. I don't have a good idea yet. We were able to develop what we were planning to. It's highly configurable. We were able to configure the workflows and orchestrations, but we are not able to run it yet. I don't want to give people the wrong impression because of my experience so far because it may not be an accurate one. It may not be the fault of the solution. When I worked with IBM in the past, it was easier. Due to the complexities, I would rate MuleSoft a six out of ten.
We're partners of MuleSoft. We provide the solution's service to our clients. The solution would be useful for large organizations. If there are more than three or four systems, and if there is an expansion, it would work best. Small or medium enterprises with two or three systems, may find the solution a little bit unorganized. I'd rate the solution seven out of ten. If the stability were more reliable, I'd rate it higher.
My opinion is that Mule ESB depends on the business and the continuity of their enrollment. If you are a system that has not much left to repair, then your products and your APIs are assets within your organization. Here in the bank, we are facing different kinds of issues when we are integrating different systems: * We are communicating with different card carriers like Mastercard and Visa. * Their standards are different according to the client requirements, i.e. exactly what kind of card they're looking for. * They can get the products according to their requirements as well as their budget. I would rate Mule ESB with 7.5 or 8 out of 10. * It's really easy to implement. * It's supporting our platforms: Windows, Linux, and Mac. * The performance. * It's free. I'm looking for an API platform that supports the whole technology as well as the next-gen. Mule ESB is lacking for self-support, self-training, and documentation. The documentation of the product is less because they're selling the training. You have to enroll for the training, then you'll get the full documentation. If you're an advanced user, you will not get much information from the public documentation.
I would rate this solution a seven out of ten.
My advice to others who are implementing this solution is to first become acquainted with the forums. There are always reports coming out about the software, and new technologies. The next thing is that I would suggest always starting with the latest version. Older versions are available, but you should install the most recent one. I would rate this solution an eight out of ten.
I will soon be migrating to version 4 of Mule ESB, although we are also interested in the WSO2 solution because it seems to be very complete. Using Mule ESB does not require somebody to be a Java developer, although there are some Java concepts that you need to know. For example, some people use JSON, and I find that they are scared of Mule ESB because it is based on Java. But really, it isn't a problem if they don't know it. This solution has good performance and support, but not everybody can use it because many of the features are expensive. Especially for application management, it is expensive compared to solutions such as WSO2. It is limiting for small and medium-sized companies. I would rate this solution a seven out of ten.