Scalability is another challenge for us. It is not scalable, not for our architecture and implementation setup. It hasn't been scalable for us.

It's used across multiple countries, so there are quite a few end users using this in our company.  

It is a scalable product that can be used by both small and enterprise companies, depending on the specific industry and their needs. For example, it can be used in healthcare, banking, or the automobile industry, and if a company can afford it, they can arrange to use it.

It is a highly scalable solution. Scalability-wise, I rate the solution a ten out of ten.

My clients who use the solution are mostly enterprise-sized businesses.

The solution is scalable. 

Scalability-wise, I rate the solution a nine out of ten.

Considering my company's clients, I think that a couple of thousand users use the solution.

It seems like our current setup has scalability limitations. We've reached the maximum capacity, so we can't scale up or out anymore. This is causing some issues, especially when dealing with large files or complex processes. For example, sending data to other systems via an HTTP feed endpoint can take longer than 30 minutes. My company has four users. 

We have about 50 users using Boomi AtomSphere Integration and plan to increase it. One technical expert and some internal knowledge of Boomi AtomSphere Integration is enough.

It is a scalable product. Users can expand it if they like.

We have around 400 to 500 users right now. We do have plans to increase usage in the future. 

The scalability capabilities are pretty good.

There aren't a lot of users that have access to the product directly. The solution is really cordoned off, meaning it's working based off of changes in the system. Everybody's using the system and making changes, and then the integration kick gets kicked off. Working on the platform, making changes, that's very minimal work and that's just me and someone else.

Currently, we're on a pretty steady path. I can't speak to if there are plans to increase usage.

We have three analysts using the platform. I rate its scalability a seven out of ten. It can be improved in terms of customization.

May have to improve on the molecule clustering communication as the cluster seems to be having problems frequently. Otherwise, the solution is scalable.

I rate the solution's scalability a six out of ten. My company has one to two users for the product. 

The Boomi AtomSphere Integration is highly scalable.

We have 10 to 15 developers who use this solution, and it is used in over 200 applications.

We have plans to expand in the future.

It is a scalable product.

I would rate AtomSphere Integration's scalability six out of ten. 

Dell is a highly scalable product. We have not seen any issues in terms of scaling the product to the enterprise level. However, Dell Boomi is not an ETL tool. It is an integration tool.

This is a scalable solution that is used by very large companies.

No scalability issues so far.

I would say the scalability, from my point of view, where you reach kind of a problem is the pricing. Because once you have a lot of integrations, your price goes up. At a certain point, you will say to yourself that it becomes too expensive. 

There are other technologies that have a different way of pricing, where you do not pay per integration, but there is a much larger initial fee. In theory, Jitterbit can scale pretty much however you want, because you have a lot of ways to configure it and to make it load-balanced and redundant and so on. Those things are no problem and there are no additional fees. You can do much more with it without additional costs. You are not limited by the number of integrations in your price level. But typically the entry-level fee to start is ten times higher to get started with Jitterbit. So a different type of client will go for that pricing model because they don't want to have to think about the pricing constraints.

The Boomi licensed model is actually about the same cost as Jitterbit in the end. It is positioned for companies with 5 to 35 integrations. Once you go above that, it becomes very expensive. If you have more integrations and need to scale more than that, I see that people would maybe want to go to other products like MuleSoft or other larger players.

We did not encounter scalability issues.

I'm not sure about the scalability of the solution. I tested it in my own environment and did not test scaling.

There were issues with the size of the logs generated. They need to improve the code.