I have worked as an Integration Architect/Developer for many years and have used Mulesoft, Boomi, Informatica, Workato, Celigo, SSIS and many other integration tools. The tool you would pick depends on the business use case. In general, there is a continuum between complexity and power on one hand and simplicity and ease of use on the other. The simpler, easier tools to use like Workato do not necessarily have the full range of power or performance for certain tasks that the more complex tools have. Mulesoft's developer tool is a powerful tool but is built on a legacy IDE (Eclipse) that is complex and not designed for non-developers to use. Boomi is probably the best example of a tool that combines both ease of use with a very powerful platform. Simpler tasks actually can be built by non-developers as it is a GUI tool. Unlike Mulesoft, Boomi was actually built in the cloud instead of being retrofitted to be an IPaaS tool after the fact. It is perfectly capable of doing ETL, Asynchronous Messaging and API-driven design and development. It is low-code and results in very rapid prototyping and development. In general, it would be my first choice of a middleware tool for most applications requiring complex integrations, large datasets, and API development when simultaneous connections to multiple systems is desired.
Technical Director at a tech services company with 51-200 employees
Real User
2020-02-20T06:38:00Z
Feb 20, 2020
This solution is made for large companies. Smaller organizations don't use these kinds of middleware applications because AtomSphere is used to integrate between large products like SAP and Salesforce. My advice to anybody who is implementing this solution is to have a very good FDD. The functional description of the business processes should be very well described before starting this kind of project. Overall, this is a very good product. I would rate this solution a nine out of ten.
Chief Technology Officer - CTO at a tech services company with 11-50 employees
Real User
2020-02-13T07:51:01Z
Feb 13, 2020
We're a partner with Dell EMC. We use the on-premises solution because of storage. In Turkey, the cloud is not available for the most part. Our customers are specifically finance organizations, and they are not allowed to use the cloud, due to country-wide regulations. Most of our implementations are on-premises. We're using the latest version to test in other environments. It's been good so far. I'd rate the solution eight out of ten. For what I've seen in the live environment, it's good. However, I'm reserving a few points to see how it goes as I learn the system.
Digital Challenger at a tech services company with self employed
Real User
2019-12-12T07:48:00Z
Dec 12, 2019
On a scale from one to ten where one is the worst and ten is the best, I would rate Dell Boomi AtomSphere as an eight. What would make it better from my perspective is not just a question of features. There is actually a problem in that market, and that is offering a tool that a company can use by themself without the help of a local partner. I think that is where Boomi as a tool might be just a bit too complex. On the other hand that is also the power of it because the complexity allows you to do more complex integrations. The nice thing is that it is not a case where you have to ask your external partner or technical person to do everything for you. It is really a tool that you can learn to use yourself. I think the point is to be sure you have enough qualified partners and resources locally who can help you when you need it. There I see that Boomi could be a problem for some people depending on location. Because I'm speaking now for Belgium and the Netherlands, in our region it is okay. It can be better, but it is okay. That is a very big point against Jitterbit. Jitterbit has almost no partners and zero in Belgium. At least not certified partners. That makes it a bit harder to get local support. And I know that for my typical customers — companies that would have from 50 to 1,000 users — that they like to have a local person who can come and coach and help and train, and then also design. In the end, the client wants to do the things themselves, but they want someone to help them to start up. That help is something they prefer in their local, native language and in their local offices. That is something that Boomi provides, even though they could be better in the partner landscape. But for Jitterbit, it is actually non-existent in Belgium. It could be much worse and much more of a problem elsewhere. There is a roadmap that I saw and it looks very good for the future development of the API, so I have the feeling that Boomi will have the API management issues fairly under control. They can always improve the number and type of connectors that they have for the integrations. What you typically see is that products have various types of connectors in e-class integration at the surface. You have tools that are very focused on sales and marketing, integrating things like your Facebook advertisements, CRM and your leads, and other kinds of integrations. That is not really where Boomi is currently positioned as a big player. There are other companies and products that do those things better. Then there are other tools that are for really big enterprises or complex systems, and these are very expensive solutions. That is also not where Boomi is positioned. Boomi is mainly focusing on integrating a lot of midsize business databases, CRM systems, ERP (Enterprise Resource Planning) and things of that sort. They do that very well. But they might want to focus also a bit more on social media and that kind of marketing tool to expand their market base. Maybe not doing that is a strategic choice. But I know that they have a lot of funding from Dell — much more funding than Jitterbit has. They must easily have ten times the funding. They have to use it to improve the product compared to the competition. So basically in the next releases, they could just improve on the partner landscape, the API management model, and maybe add more features for versatility to do more than they do now.
The Boomi AtomSphere integration platform as a service (iPaaS) supports all your application integration processes – between cloud platforms, software-as-a-service applications, and on-premises systems. Your entire team has online access to a powerful range of integration and data management capabilities, that can be realized in a fraction of the time of legacy middleware technologies.
I have worked as an Integration Architect/Developer for many years and have used Mulesoft, Boomi, Informatica, Workato, Celigo, SSIS and many other integration tools. The tool you would pick depends on the business use case. In general, there is a continuum between complexity and power on one hand and simplicity and ease of use on the other. The simpler, easier tools to use like Workato do not necessarily have the full range of power or performance for certain tasks that the more complex tools have. Mulesoft's developer tool is a powerful tool but is built on a legacy IDE (Eclipse) that is complex and not designed for non-developers to use. Boomi is probably the best example of a tool that combines both ease of use with a very powerful platform. Simpler tasks actually can be built by non-developers as it is a GUI tool. Unlike Mulesoft, Boomi was actually built in the cloud instead of being retrofitted to be an IPaaS tool after the fact. It is perfectly capable of doing ETL, Asynchronous Messaging and API-driven design and development. It is low-code and results in very rapid prototyping and development. In general, it would be my first choice of a middleware tool for most applications requiring complex integrations, large datasets, and API development when simultaneous connections to multiple systems is desired.
This solution is made for large companies. Smaller organizations don't use these kinds of middleware applications because AtomSphere is used to integrate between large products like SAP and Salesforce. My advice to anybody who is implementing this solution is to have a very good FDD. The functional description of the business processes should be very well described before starting this kind of project. Overall, this is a very good product. I would rate this solution a nine out of ten.
We're a partner with Dell EMC. We use the on-premises solution because of storage. In Turkey, the cloud is not available for the most part. Our customers are specifically finance organizations, and they are not allowed to use the cloud, due to country-wide regulations. Most of our implementations are on-premises. We're using the latest version to test in other environments. It's been good so far. I'd rate the solution eight out of ten. For what I've seen in the live environment, it's good. However, I'm reserving a few points to see how it goes as I learn the system.
On a scale from one to ten where one is the worst and ten is the best, I would rate Dell Boomi AtomSphere as an eight. What would make it better from my perspective is not just a question of features. There is actually a problem in that market, and that is offering a tool that a company can use by themself without the help of a local partner. I think that is where Boomi as a tool might be just a bit too complex. On the other hand that is also the power of it because the complexity allows you to do more complex integrations. The nice thing is that it is not a case where you have to ask your external partner or technical person to do everything for you. It is really a tool that you can learn to use yourself. I think the point is to be sure you have enough qualified partners and resources locally who can help you when you need it. There I see that Boomi could be a problem for some people depending on location. Because I'm speaking now for Belgium and the Netherlands, in our region it is okay. It can be better, but it is okay. That is a very big point against Jitterbit. Jitterbit has almost no partners and zero in Belgium. At least not certified partners. That makes it a bit harder to get local support. And I know that for my typical customers — companies that would have from 50 to 1,000 users — that they like to have a local person who can come and coach and help and train, and then also design. In the end, the client wants to do the things themselves, but they want someone to help them to start up. That help is something they prefer in their local, native language and in their local offices. That is something that Boomi provides, even though they could be better in the partner landscape. But for Jitterbit, it is actually non-existent in Belgium. It could be much worse and much more of a problem elsewhere. There is a roadmap that I saw and it looks very good for the future development of the API, so I have the feeling that Boomi will have the API management issues fairly under control. They can always improve the number and type of connectors that they have for the integrations. What you typically see is that products have various types of connectors in e-class integration at the surface. You have tools that are very focused on sales and marketing, integrating things like your Facebook advertisements, CRM and your leads, and other kinds of integrations. That is not really where Boomi is currently positioned as a big player. There are other companies and products that do those things better. Then there are other tools that are for really big enterprises or complex systems, and these are very expensive solutions. That is also not where Boomi is positioned. Boomi is mainly focusing on integrating a lot of midsize business databases, CRM systems, ERP (Enterprise Resource Planning) and things of that sort. They do that very well. But they might want to focus also a bit more on social media and that kind of marketing tool to expand their market base. Maybe not doing that is a strategic choice. But I know that they have a lot of funding from Dell — much more funding than Jitterbit has. They must easily have ten times the funding. They have to use it to improve the product compared to the competition. So basically in the next releases, they could just improve on the partner landscape, the API management model, and maybe add more features for versatility to do more than they do now.
I would like to see dramatic improvements in API management so that the product suite can be on top.