The solution is highly stable. I rate the stability a nine out of ten. 

Compared to on-premises, the cloud solution is not as stable. These days I see a lot of network issues and cloud servers going down, becoming unreachable for whatever reason.

Overall, it's very incredibly stable. I've never seen any other software platform that can run for so long without crashing. We've had servers run for over a year, and we have restarted them not because they were broken but because we were installing something. We've had servers run for over a year.

In terms of support for the solution’s adapters and connectors and long-term stability for your services or integrations, you build once and forget it. 

Its stability is very high. It is very stable, and I've never seen it crash. In my 12 years of career, there have been hardly one or two instances where there was an issue, but that was also because of some issue in the development where we had memory leakage.

Given that we have been using it all these years, you can imagine the stability of the system.

We experienced major issues at the beginning of the implementation when the product was still kind of new. But over the years they improved a lot. 

They keep producing new versions at a rate that we cannot keep up with. That is a problem for us because they have a very small set of supported versions. That is a downside of their products. Old versions are supported for a very limited time. They keep telling  us, "You need to upgrade." But we do an upgrade and they introduce a new version and the one we updated to is already obsolete. Their life cycle is very short.

The stability is very good. 

The solution can be prone to bugs, especially if you customize it.

Performance-wise it was fine. We don't have any problem in that sense. Stability is related to the architecture and all that, so we had to federate it properly so we did not have any performance issues. 

When we started with Integration Server, it was around version 27 or something. Right now, it is around version 40. That's an indication of how many fixes there were. Certain headers were not supported. SSL handshakes had some performance issues and things like that. Those were the kinds of issues we dealt with.

Software AG is a partner who has been around for many years. The company is not going anywhere. Regarding the solution, you can get the capabilities that you need out of it.  It is a known solution that works really well and does exactly what you would expect it to do.

Software AG's full support for the solution’s adapters and connectors brings long-term stability to our services and integrations. Software AG has many SMEs in each region, both globally and in each product type. Being able to have access to a subject-matter expert in the specific tool or region that I'm looking for is invaluable. I feel like I am talking to someone who has hands-on experience in either developing the solution or has many years of experience with the product or similar customers. They also have people who just work in specific business groups. For example, if I'm looking for a knowledge worker to do something with IoT, then they have people ready who can answer specific questions about products that we might be looking to integrate with.

The product's on-prem version is more stable. The cloud version was introduced only recently and will take time to establish itself. I rate its stability a six out of ten. 

webMethods Integration Server has been around for quite some time, so it's a very stable solution. It's much more stable compared to newer entrants in the market.

For software to be stable, it has to be deployed. It has to be created, developed, tested, and deployed in production. Then, it'll be patched and versioned across multiple years, so the more versions a solution has, the more bugs have been removed in the core system, making it much more stable than newer competitors. Again, this is a case-to-case basis, but you can generally use this as a rule of thumb. The longer the software has been there, the more stable it is.

This is why the backend payment systems are written in COBOL in almost every top financial organization or bank you walk into. Even though COBOL is practically a dead language, it's very stable because it's been in production, and it's been tested, verified, and used; plus, its bugs have been fixed over a long period, so you have very, very stable systems that run on COBOL.

I am very satisfied with stability. It's very stable, we haven't had any issues at all.

We had a lot of issues with our other solution but none with Integration Server.

I would rate the stability very high. Once it is running, it's very stable.

The webMethods Integration Server is a tier-one application and if it's down, impacts pretty much everything. When it runs, no one knows about it but if it goes down, everyone screams. It is very crucial.

I rate the solution a six out of ten for stability.

webMethods Integration Server is stable.

webMethods Integration Server is a stable solution for our usage.

It has been very stable.

The solution is very stable. I'd rate the stability ten out of ten. There are no bugs or glitches. It doesn't crash or freeze. 

webMethods Integration Server is quite stable, especially given the amount of load it has been handling.

webMethods Integration Server is very stable as a product.

If it's set up properly and if you do it in a good way in large-scale organizations, you need to have a maintenance team that is doing the maintenance and support. If it's working properly and updated properly with the latest versions of updates, then there should be no issues with using it. It is reliable. One of the main benefits of Integration Server is that it is reliable.

I would rate it an eight out of 10 in terms of stability and scalability.

This is a stable solution.

We haven't had any issues. Everything has been working. We like the new version, the new upgrades. It seems they keep improving upon things. We've put in high-availability and fault tolerant solutions so we have had zero downtime due to the system itself.

We have no complaints about stability.

ESB is rock solid. Products on top of Integration Server have much less stability.

The product is very stable. 

It is stable, but it depends on the development team, not the platform itself. The platform itself is stable and has been used before by a lot of big companies and entities, but the old integration services are not related or tightly coupled with the platform itself. If you don't have good developers that can implement a good architecture or a good design, you will have issues.

Regarding the Stateful session inbound to ESB (Integration Server). It seems that the Stateful session sometimes doesn't die out when the transaction is finished, but waits until the timeout expires (although quite often it doesn't even died even after timeout expires, which eventually would flooding the server).

It is stable. They are rather aggressive in their patches and upgrades.

I rate the solution’s stability a ten out of ten.

The solution is very stable. They have the flow language. We've been using it since version 6.0 and we haven't had any major issues. It's pretty seamless. 

The stability of the webMethods Integration Server is good.

This is a stable product. The Universal Messaging component had some issues with stability, although they have now been fixed. Over that time, they disappointed the customers for about two years.

We are still in development and trial. We didn't reach the point of production where we could really gauge its reliability and therefore we didn't really know how stable it is. We're still in the early stages.

No issues with stability.

There were no stability issues.

The stability of the webMethods Integration Server is good.

Very often there have been stability issues, but typically the source of problems was in the IS configuration or deployed services. Many of problems exist only in AX system (IBM JRE).

No.

Yes, there is still plenty of room for improvement in MWS, SAG Designer.

Yes, somewhat.

The solution is very stable.

No problem with stability in versions 6 and 7.