Qlik Talend Cloud Reviews

We have multiple use cases for this solution. We integrate with Salesforce, SAP and Oracle databases to build business logic and provide reporting.

The transformations are built in and come as a package for us to drag and drop and complete in one go. The main platform of this tool is Java and if you know how to use Java, it will be a very easy tool to use.

Sometimes there are bugs which are unidentified and we have to follow-up with the Talend team to resolve them. In a critical situation, it takes time for them to update patches. In a month, we get two or three patches and this means we need to redeploy completed jobs. 

I have been using this solution for three years. 

This is a stable solution. 

This is a scalable solution. 

The technical support team are very supportive and respond quickly based on the severity of the ticket we raise.

This solution is very easy to set up and deployment is quick. 

Deployment was completed by an in-house team. 

This is a good tool. If your use case depends on heterogeneous sources like Salesforce, SAP, and some other product information systems, I would recommend Talend. 

I would rate it an eight out of ten. 

My main use of this solution is application integration.

I like everything about this product, but the biggest thing is the ease of use. I also like the ability to have files between Linux missions.

An area for improvement would be that securing the product can be challenging because there are multiple ways to secure everything. If they offered a secured version or sample, that would be a big improvement.

I've been using this solution for around ten years. I use it myself and have trained others in how to use it.

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.

Currently, scaling is more effective with the cloud version, where you can get into the data fabric and have access to more power.

I've had no problems with tech support - they're willing to work with me as an advanced user to figure out solutions.

Talend is scaled much lower in cost than Informatica.

Talend is getting ready to drop SVN as a code repository in version 8 going forward, so you have to convert anybody who's using SVN to switch over to GIT (on which it runs much faster). I understand it isn't easy to get people who are experienced in this product, so you should go through the training on their website as there are a lot of nuances in this product that you may miss otherwise. I would rate this solution as ten out of ten.

Talend Cloud Integration was around when a few of our teams wanted to use the remote engine concept on AWS, and with the on-premise we could not do that. They wanted to use Talend on AWS, where they wanted to spin up their own job servers and to process their own data on the cloud, on their own BPC's. They felt that the transitions happening between on-premise to cloud would be more expensive than if they did it from cloud to cloud or from their VPC to remote engines, building up remote engines. So one reason we switched was cost and the second was that there is no dependency if the job servers go down on on-premise and the business could get impacted. Here, there is none of that. It was a kind of seamless integration between cloud to cloud environments and all those things.

In terms of valuable features, when comparing PMC to TAC, TAC is more centered around the user configuration than the project configuration. If you look at the Talend framework as a whole, you need your Talend administration center, you need a Studio and you need job servers. But there are a few things with respect to job rules, profiling, and project creation which are more advanced in PMC versus TAC. When I say more advanced, in the normal Talend administration center you do not have a super admin and you can have multiple admins who can control their own application. Today, if Talend is used by 10 different applications on TAC, one admin can create those projects for those teams and all other elements which are on-premise. There, you can create multiple admin rules where each application can have its own admins and they can take care of their deployment and they can manage their own environments, etc.... But on the on-premise solution you do not have that, which is a disadvantage.

Let's say in an organization there are multiple applications using Talend. If you run on TAC, you have one admin who has to manage all these projects - assigning projects, creating user rules, providing them access to different environments, you have a dev test and fraud environment. All those things have to be managed by a single admin or maybe one or two admins who have access. But in TMC, which is the Talend management console, you can create sub-admins.

One would be a super admin and you can create those sub-admins who take care of all these things. If I have five applications that are using this solution and I am the admin I don't have to understand their use case and how they want to deploy and all those things. I just give the rules to that admin and that admin takes care of everything. The super admin gives it to those application admins and the application admins can take care of their environment, their deployment process, and creating user rules, etc...

Another thing about the cloud solution is that you don't have to worry about any upgrades. On-premise you have to upgrade your TAC and then you have to upgrade your Studio, which is an effort and time consuming. But on cloud there are automated upgrades, where they get automatically pushed. Then with the Studios, you have to just upgrade that. That is a backwards compatibility. For example, if your Studio is on 7.1 and then the remote engine is on 7.3, that is a backward compatibility. But it's advisable to upgrade your Studios as soon as your cloud instances get upgraded.

In terms of what could be improved, there is not much. It's a basic server setup. It all depends upon what kind of software you want to put on that server. With the remote engine you are building an EC2 or you are setting up an EC2 instance and then pushing all your software there and then running it from there. I don't see any challenges with that.

I have been working with Talend Cloud Integration for about 3 years.

I haven't seen any issues with stability, it's pretty stable.

The scalability depends upon how many you have. If you are looking with respect to performance, the scalability can be whether your job servers are always available, then it is scalable. But if you're looking with respect to performance and you need more job servers, you have to strategize it in a way where you get more tokens to spin up more remote engines.

In terms of pricing, they have the concept of tokens. They give you a certain number of tokens per license. If you have less tokens, then you will have less servers for execution, and that also ties back to the number of licensed servers that you have procured. But if you want more tokens for the remote engines, I think it is around $2000 for maybe 10,000 tokens or a hundred tokens, I don't remember so don't quote me here, you have to pay more to acquire more tokens.

My advice for anyone implementing this solution with respect to the remote engine and TMC connections is that it all depends upon the enterprise. Whether they have single VPC's where they scale up or multiple VPC's where they want to spin up. The cost increases or decreases based upon the strategy. So if I have my remote engine set up on-premise and I want to run the jobs from cloud, the cost will vary, and if you have the VPC to VPC connection then your cost will remain the same. With respect to reliability and with respect to scalability, if you need more job servers, let's say you are trying to process some terabytes or gigabytes or petabytes of data, and if you have two or three Talend licenses on cloud, then I would recommend buying more tokens so they can spin up more remote engines.

The tokenization and the detokenization also apply with this solution like in the 7.3.

I would rate Talend Cloud Integration an eight. The reason is that there are no concurrent licenses, they only have seat licenses on cloud. That's the whole challenge. For example, if in any project your headcount increases or decreases, you do not have that concurrence and you have a seat license, you run into challenges because you have to procure a few more licenses for getting the job done. That's why I would rate them at eight out of 10.

I'm very passionate about this solution because if you look at any other tool that costs around $200 - $300,000, like Delphix which costs you a million dollars, Talend is very cheap and is almost is at par with what others can do. There is one thing which Delphix does which Talend cannot do, but overall, I would say apart from that, if you're looking for a solution, you should give it a try.

We use Talend to help our clients distribute their products.

It's a real ETL solution. You download data, transform it, and then you upload it.

The most valuable feature is integration. There are several connectors, there is a large community, and the solution updates often. It is always up-to-date.

Performance and speed could be improved.

They could improve on the scalability.

I have been using the Talend Data Management Platform for three or four years.

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

It's scalable but they could use Docker to improve the scalability.

I have contacted technical support on occasion. It's great because you have the support and you have the community as well.

You create a ticket and intel is very open and reactive. They are friendly.

The initial setup is straightforward and not complex.

It did not take a lot of time to deploy.

Before choosing Talend, we evaluated DataStage and Informatica.

We decided to go with Talend because it has an open-mindedness to it. It's not a closed system, you have a great community and in France, where I live, it is the leader and there are many people who can do a good job using Talend.

Talend is a good product and I recommend it. It is an open system, you have several connectors, it's evolved, and you are unlimited because of the great community. There are always people who may have had some of the same encounters and have found solutions to the same problems. 

I am still learning this product myself, I have not yet used all of the features this product has to offer.

I would rate this solution an eight out of ten.

Data Quality easily identifiable instead of manual finding and cleaning the data through Excel (earlier used to follow) before ETL

Currently the best open source data quality tool available as compared to other open DQ tools ('DataCleaner', 'Open Source Data Quality & Profiling') for of a variety of reasons:

1. Vast connectors to different DB, Web, CRM, etc
2. Custom code is allowed
3. Wide range of advanced algorithms
4. Recommended for advanced users
5. Detailed analysis, etc
6. Large community of users

The most valuable features for us are: custom code, connectors, algorithms.

As it is a open source tool, some minor bugs are there.

Fairly straightforward. Lots of user guides and tutorials are available to get started.

The best part is that it is open source.

Great product, surely give it a try.

The solution is customizable.

I have been using Talend Data Quality for approximately four and a half years.

The performance is one area that Talend Data Quality could improve in because large volumes take a lot of time.

I have not needed the technical support.

The implementation is not difficult, it has been straightforward for the implementations we have done.

We do the implementation of this solution.

I rate Talend Data Quality a nine out of ten.

Currently, I am using this solution to develop an integration between two particular systems. It's selecting a TSV file from slate and transferring to banner after you work the data.

Since I am using it for an ongoing project, I haven't been able to deliver on that project.

It is going to help us in changing the way we look at integrations and not have deployed from a strictly coding standpoint. Instead, it's going to be from a perspective of design and orchestration, which is the direction we are going in.

I have been using very basic features, but one of the features that I liked the most is how it handles different contexts. I like the way that you can use the context variables, and how you can work those context variables to give you values and settings for every development environment, such as PROD, TEST, and DEV.

The objects are friendly to use, and another feature that I like is the general generic schemas, even though it took a certain amount of learning to get used to it, it was beneficial.

With what I have seen in the cloud version the interface is great, and what I have used of the on-premises version is great.

It's user friendly.

While I understand that I am using the open-source version, but the facility of having version control is to the point where you can share it with other developers in the team. I think that's the way the product was intentionally made. That way you don't have organizations using the open-source version and instead of using the paid version.

I would like to sync a project and do an upload from that current version, and then from GitLab, be able to download the latest one. It will make it easier to share code with teammates. This is most likely something that Talend Open Studio doesn't have intentionally so that organizations have to invest in the cloud.

If Talend were to be able to offer an annual license in which the number of integrations is the deciding factor, instead of the number of concurrent users developing, then that would make them a little bit more competitive when you're comparing them to, for example, were Workato or SnapLogic.

I'm still in the learning phase and the exploration phase. I have been working with this solution for approximately a month and a half.

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.

In terms of scalability, we have put basic projects in Cron Servers to run out a Cron Job, which didn't require a lot of work. I had to do the research on how to export the job, then it worked. We have only done it with basic jobs where you are moving files over, creating directories, and validating if the directories exist.

Soon we will be deploying one that is going to involve connecting to an SFTP to select files, doing a DIFF of the file, and comparing it to a previous version. With what is left, we're performing inserts and Oracle tables.

I am the only one that is fully using this solution. I do have another person who helps me when transferring files to the Cron Server.

I really haven't reached out to technical support. I've been just doing it on my own, going through forums, blogs, reading multiple books, and finding a couple of videos on YouTube. That has been enough.

I would have to encounter something that is challenging in the development process, and since I am going to be using some APIs, those calls would be done through SQL. I don't think that I will be asking for help anytime soon, but it might be different once we are using the cloud version.

We are currently in the process of selecting an I-PASS solution and right now, the Talend Data Management Platform is one of the finalists.

We are ironing out the differences and seeing how much we can do with the open-source version before moving onto the cloud version.

In the initial setup, I was having some struggles with making sure that Java requirements were properly set up. After that, it was working fine. 

I have installed it on both a Mac and a PC, and I haven't had any complaints. 

I'm still working out the dynamic of using a GIT repository, such as GitLab to be able to back up all of the projects that I'm working on.

The pricing is a little higher than what I had expected, but it's comparable with I-PASS competitors.

It's on the higher side because it's a developer-user licensed solution. It makes you look at the investment differently than an I-PASS that is offered by the number of integrations that you have to work on. You have to balance it out on one end. You have an I-PASS that tells you that you can have an unlimited amount of developers, but you can only develop a certain amount of integrations per yer. That's what you are paying for.

With Talend, it's the opposite. You can have an unlimited amount of integrations but you only a license for two developers, for example.

For anyone looking to use this solution, I would suggest using the open-source version first.

I have been told that there are missing features, but I haven't found what those components are. I can understand how an organization that is already living with the Talend cloud can identify that easier because they were already facing a challenge without finding that component.

The reason why that organization told me that was because they have three developers working on a cloud version and one developer working on the on-premises version. 

That is how they picked up on it. According to what I had heard from that source, there are differences. There are some components that are only going to be available in the Talend cloud version.

At this time, it is difficult for me to evaluate this solution, as I have only seen how their products work and I am not fully working with Talend. It's subjective. 

The only way that I could be objective would be if I had maybe one year of experience using a different I-PASS and then one year of experiencing using this one.

We are still in the process of evaluating them, but I love the way things look in Talend, and I'm all for Talend. I know that Workato is really close to it as well.

The relationship with the vendor is currently coding, presentations, demos, and conversations of how this I-PASS can be a part of our organization.

I would rate this solution an eight out of ten.

I was using the Talend Data Management Platform to ship data from the source to the website, and I was using the Talend administration console to monitor the different data flex and developing new data flex.

The new data flex was deployed to our servers. We are also using the same Talend administration for tasks, monitoring the tasks, and for developing the tasks.

We have four to five servers running on Talend.

The features that I like the most are the simplicity of the interface, and the ability to quickly develop with a predefined component.

Having the ability to mix both my own code created in Java with the predefined components is helpful.

It is easy to face issues and meet any of the client's needs.

We were using TAC for the testing environments and another TAC for the production environment. We had to promote our code manually from one environment to another.

I would like to see them add a feature in TAC that exists in TMC where you have the ability with different environments to promote code easily from one to the other.

They lack in memory capacity. We had to add a new job server to deal with the new system we had.

I would like to see components added with routing and web services. We have many subsystems that are not being used with Talend to make them communicate. It would be better to have unified systems within Talend to be able to do so. Having it directly in Talend Data Management would be nice, or an ESB (Enterprise Service Bus) or some web service applications. Also to have a unified TAC, actually just having one environment or one Infospace for the entire environment.

This solution is scalable. When we had to add new data flex we were just parallelizing, having different jobs running in Talend on five different job servers.

I haven't had the need to contact technical support. When I have had issues, the Talend portal is there and there is a Talend Help Centre where you have discussions and blogs. I was able to find answers there. 

Previously, we were using TAC (Talend Administrative Console).

License renewal is on a yearly basis.

I have never spoken with Talend technical support directly over the phone or by mail, I was able to find my answers on the web. Overall, I am satisfied with Talend and I recommend it.

I would rate Talend an eight out of ten.