I would rate the scalability a nine out of ten. It is a scalable solution. We have clients on the bank side. They are mostly in the public sector.

I rate the solution’s scalability an eight out of ten. Almost 80% of the people in our organization are using the solution. We have more than 100 users. Our clients are enterprise businesses.

I would rate the scalability a seven out of ten. It's not much more dynamic, not as dynamic as you may think, like seeing it in the cloud.

In order to use it, you need to have the download servers and then scale up your systems.

Oracle SOA Suites serves as a middle layer between applications. For example, let's say you have SAP, and we have Salesforce or Oracle ERP system. Users connect to those systems and perform certain activities or transactions on the applications. Now, if any data needs to be synchronized or any integration needs to happen between these applications, we use the Oracle SOA Suite. It acts as the bridge between the applications, not between the users. It's like having endpoints between the applications. Currently, we have 20 endpoints; 20 systems are connected to it, which is great.

Oracle SOA Suite is being used daily. We are using it to its maximum potential. 

It is not that scalable and requires rework and additional servers. We have about 30 users and don't have plans to increase the usage. We needed about eight people for deployment, mostly database admins and an Oracle expert.

Scalability is a challenge for Oracle SOA Suite.

No issues. We were able to scale out using multiple application and web servers balanced by hardware load balancers and Weblogic clustering. Similarly, we were able to deploy the database on Oracle real application clusters, allowing scale out of the SOA Dehydration database.

You can use whatever OS system you would like. You can use Linux or Windows. And, at the same time, you can try to grow with nodes, if you need it with a load balancer. In the end, you have the facilities to grow in the future. We have several hundred individuals using the solution daily.

I didn't have any problems scaling Oracle SOA Suite, so it's a ten out of ten for me, scalability-wise.

Since we are using the solution on-premises, scalability may be the real challenge. We are moving towards using the cloud or Oracle cloud, so maybe the scalability will be easier if we move to the cloud. This challenge isn't caused by Oracle, it's because it is on-premises. I don't want to blame Oracle for the scalability challenges.

Once correctly configured, scaling and stability have not been an issue. When issues have occurred, we have traced the problems back to poor deployment configuration, particularly environment factors such as the network, etc.

It's been able to scale for our needs.

The solution is moderately scalable. However, it is not effective. The solution must improve the scalability. Around 20 to 25 people use the solution in our organization.

The solution is stable. It is very unlikely that you will face any product issues or see any unwanted exceptions. I rate the stability as nine out of ten.

It’s a very scalable application.

An effective alert mechanism needs to be put in place for deployment and to help scale environments.

Scalability and Stability are linked to each other as they impact each other.

It is scalable. You have to spend a little more money to scale it up. Our system handles transactions and products both. If we segregate and have parallel systems(servers) for transactions v/s products, it can be a better performing system.

We haven't needed to scale it.

This solution is scalable if it is designed well.

Three people are using the solution.

Oracle SOA has been a rock solid enterprise-level tool for many years. It's really foundationally built on WebLogic and so it has a lot of scalability built into it. I've seen implementations that support millions of transactions per day, hundreds of trading partners, hundreds of web services and APIs. The scalability and the ability for capacity growth has always been there and has always been a fundamental tenet and one of the fundamental principles of Oracle SOA Suite. Because it is an enterprise service bus, it has to be able to have that level of scalability. The implementations really are dependent on what the customer use cases are. Because it's such a feature-rich product there's a lot you can do with it and there's a lot of good ways to implement SOA and there's a lot of bad ways to implement SOA.

We do not have many integrations. We have a very small team and we have four or five consultants working for us. Together with a couple of people in our organization, there are six or seven people who have access to manage.

Good performance when using cluster environment.

One of the reasons why we went to Oracle SOA Suite is its ability to scale out to all the different platforms and technologies. I think it's doing pretty well. We have integrated with a couple vendors right now, and we plan to integrate another five or six in the pipeline.

We haven't really had to scale it because we're not using it that much yet. We may have plans in the future to.

So far, it has been a scalable solution. The next few years will be the true test of it, but so far, it has been a scalable solution.

No issues noticed.

It is scalable.

There were issues scaling, but mainly because the customer didn't set up the product properly, and didn't do capacity planning properly. If the product is setup properly according to the right capacity design, it scales as expected.

Scalability is one of the strengths of the product. We did not encounter any issues with scalability.

It's been able to scale for our needs.

The solution is highly scalable because I'm using three nodes, three physical nodes, or virtual machines, and if I want to add a fourth one, I can add it very easily. You can add more nodes and more managed servers. We call them managed servers, without any downtime. We have more than one node, and maintenance becomes very easy. If your architecture is done well everything will work perfectly. For example, installing the solution on at least two nodes for higher availability is scalable.

We have approximately 300 services running and the number of users can vary. The user count can vary because different applications can call the same service, we reuse these services. For example, at any one time, we could have approximately 50,000 messages passing through in about 10 minutes every ten minutes.

We have had no issues scaling it for our needs.

We've had no issues scaling it for our needs.

As of right now, currently we do not have too many composites. We have probably around 20 composites in each instance. We have three different domains. If we need to scale it higher, we should be able to do that pretty nicely.

Only when the customer did not follow recommendations from the provided Enterprise Deployment Guide were there scalability issues. The new version 12.2.2 is expected to provide multi-tenancy for SOA Suite, which improves this even further.

It's an extremely scalable product. We have projects with very high throughput, and also there's a lot of tuning possibilities to make the messages extremely fast.

SOA Suite is not so much for the number of users. It's for the number of integrations that you process, as the metric is different. You don't use SOA Suite with end users in mind, as it's an integration platform. It has support for a wide number of applications from legacy mainframes to modern ones such as Salesforce.

We had no issues scaling it.

Yes.

It's been able to scale for our needs.

It is very scalable.

It’s a scalable application.

We've had no issues scaling it for our needs except with BAM.

There were no scalability issues.

We don't have that many functional users using it, so scaling has not been a true issue for us.

It contains good options for handling scalability. We haven't had issues scaling it as necessary.

12c has improved scalability dramatically and now uses fewer server resources. Also, Enterprise Manager provides better tools to monitor load.

There were no issues with scalability.

It’s scalable. It will meet the company's needs moving forward.

It scales sufficiently for us.

The organization by logical domains based on WebLogic is definitely a key factor for the scalability of the solutions.

We don't need to scale it as we haven't needed to yet.

There have been no issues scaling it.

Yes, cloud backups have issues.

Scaling is a breeze. It's very quick to add extra application servers without even having to make the system unavailable.

We have had no issues scaling it to our needs.

Scalability is medium, mainly because of cost.

It scales well to our needs.