The stability does depend on the features. Some features are not as stable as they could be, and some are not backward compatible. If there is some mismatch, it can break. You do have to update everything separately, and it is important to update from the same source.

It all comes down to how you set up everything. 

Some features are really stable. Some features are not backward compatible. One of the issues that I am currently facing is making sure that the API pipelines that we have created are version compatible with the run time server that we have installed. Ffrom a readability point of view, if you have to upgrade each and every thing separately, it's hard. There is a little bit of room for improvement when it comes to upgrading from the same source. That said, it depends on how you are setting up your environment.

We currently have the data integration environment and the remote engines and everything set up so that our upgrades happen using just one script. For Runtime, that is not yet done. This is something which we are doing currently. So stability totally depends on the way you configure it. Of course, there is room for improvement from the Talend side as well.

The stability is rated an eight out of ten. 

It's stable.

The stability of the solution is excellent.

It is stable and reliable. There are no bugs or glitches. It doesn't crash or freeze. 

I rate the tool’s stability a nine out of ten.

Great stability. As long as your infrastructure is good, then Talend will be great.

I've had some issues with bugs causing crashes, especially when making changes to the system or with the monthly upgrades to Studio they've introduced. However, the stability is great when you scale up to more users or more data.

The stability is good but the performance is slower when I work on a huge amount of data. So I think this area needs some enhancement.

This solution is stable, although not the best. I'd say that it is great but not on the top.

The Talend solution has been very stable. We have very few issues with the systems running the jobs. Most issues we have are with unknown changes to source systems that Talend jobs interact with.

I haven't found any bugs or glitches so far. I am still exploring the tool.

I've heard from organizations that have the cloud version, that there are certain objects that I will not have in the on-premises version. I don't know which objects they are. 

I still haven't seen Talent Open Studio lacking in anything, but I guess that they've gone through something specific.

I am sure that there is a generic object that you can use to cover a certain demand.

As I mentioned, we've only been using it for a year, and for a portion of that it was still in development, but it's been fairly stable in the last 10 to 12 months.

no