IBM Business Automation Workflow is a stable solution.

I would rate the stability a seven out of ten. From time to time, there are problems, and we have to reach out to support.

The stability has improved a lot throughout the years, so I would rate it eight out of ten.

We have not had any problems with the product's stability; it is very stable when it is properly maintained. I give the stability a nine out of ten.

IBM Business Automation Workflow is stable because the different infrastructure elements, such as the OS and middleware have been used for a long time.

The stability of IBM Business Automation Workflow is a four out of five

This is a new product, so we are getting a couple of bugs on the product level. We have spoken to IBM and it's up to the product vendor to provide product complications, like deployment snapshots and where we have automation in the process. We keep talking to the IBM guys to write a PMR and get it refurnished. 

We use the auto-scaling mechanism. So maybe the volume is too high for utilization and we use the load balancing, distributing the load balancing to multi-use cloud packages. We use that for the availability.

The solution is being used country-wide. That means five to eight million people use it on a daily basis. Globally, we implemented it for the National Bank because it exists across all the countries and all the 128 branches in the different countries.

It is stable.

I would rate the stability capabilities nine out of ten.

The solution is stable. IBM leads when it comes to automation.

The product is extremely stable. Obviously, there is always performance tuning and things that happen over time. Usually, if there is any major issue, it's usually the database's fault, but the impact of it is that your product goes down. You have to monitor the database and that is the area which people often forget to do.

IBM Business Automation Workflow is very stable.

It is a stable product. We have not had any issues.

The stability is fine. I have not seen any examples of an unstable BAW.

This is a stable solution that we have been able to use as a distributed system. Each silo works independently and updates are all pushed to the cloud. In the event that there is a shortage in communication, the silo is able to operate completely independently from the headquarters.

The level of stability varied at first. Initially, we had issues in terms of setup and things like that. Now, as time has passed, I believe it has improved. 

We might have had issues because of a lack of knowledge on our part.

From the second year on, we haven't faced any issues with stability. We now consider it to be quite stable. 

The stability is average. Once it's up and running and stable, it remains stable. But there's a little bit of extra effort needed to deploy and manage and configure both the on-premises and cloud solutions.

This solution is really stable.

It is very stable, as long as when you build it, you adhere to best practices and build things correctly. I can't say it enough, "A tool is only as good as how you use it." It is a good tool.

It is stable.