Talend Data Management Platform Reviews

Our primary use case of this solution is data integration and managing historical data.

It is a very powerful solution to manage historical data and this is one of the key features that I love the most.

An area that needs improvement is the administration of data and granting permission for the different developers working on the product at the same time. Talend is a great development tool but the administration, access rights, synchronization and phoning can be better. 

New features I would like to see is changing the data capture and different connection abilities to the Oracle database because some connections are suitable for one customer and not for the other, as it is based on the environment architects or on the customer. 

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.

The solution is scalable, and we have about three to five licenses per client.

I would suggest enhancement and improvement in the support program of Talend to have a real Talend expert working with the consultant on the support process and the support to share the knowledge with the consultants. It is very important for Talend to build a good technical team for support. This is the first impression for any customer working with a vendor. So having a very good technical support team on your side will increase the trust of the customer in your product, even if there are many bugs in the application or the environment itself. I think that the system needs more enhancement and more improvement in this aspect. We need to have more cyclical documents written in a very good manner to share the knowledge between the support and the consultant implementing using Talend.

I used Oracle Data Integrator and IBM but I replaced it with Talend. I like that Talend is straightforward. By using Talend we can simulate the theoretical information with the practical exercise. 

The initial setup was easy but I would suggest developers to include two different types of installation for the product, like to be able to do silent installation and not interactive installation for both. This is very important for us because when we do the installation and have a lack of resources, the inclusion of silent installation for the product will be great. 

I think Talend is one of the easiest tools for faster implementation compared to other tools.  For example, if we're implementing the data integration solution with some other tool, it will take 10 days. But with Talend, it will take less than 50% of the time. So the tool is very easy, the interface is user-friendly for the developer and suitable for the development of the solution. That is one of the key benefits of Talend.

I recommended Talend for two of my four customers during the last four years. I replaced the Oracle Data Integrator and IBM with Talend. 

My rating for this solution is eight out of ten.

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.

Initially, it was data integration for academic data to an EDW on Sybase IQ for reporting purposes. Now it has evolved into data integration for both application and user consumption, loading data into Sybase and MS-SQL data stores. We use Studio on Windows with Servers on Ubuntu. 

This solution has allowed us to use more technical individuals for data integration that don't otherwise have expertise in SQL, Stored Procedures, and/or Perl scripting. It has improved our ability to integrate data from multiple systems and decreased the time it usually took using other means, which involved Perl or high-level SQL techniques.

The most valuable feature is the Talend Admin Console (TAC). It connects Studio to SVN (Code Repository), Nexus (Artifacts/Build Packages), and Job Servers (Runs Nexus packaged jobs). TAC also manages user access to projects, which allows multiple users, working within the same project at the same time, while maintaining all code changes in SVN. 

Talend Studio has the ability to connect to almost anything to integrate data from files, databases, web services, etc.

The documentation from version to version could be more accurate. I have found information that is inaccurate or doesn't apply to the version I am trying to install or work in. Documentation could also be more user-friendly as it seems cumbersome with too much information, which probably is why I have found inaccurate information.   

The application installation process needs improvement. They have an easy "non-secure" installation for trying out the subscription version. I would like to see installation instructions for a Production environment with system and server layout using SSL Security. It would go a long way to understand what Talend envisions as a best practice for a production environment. 

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.

It is scalable but we have not had to use it. Our next upgrade will likely be with their Cloud solution if not using Docker Containers.  

In the beginning, Customer Support helped a lot. Now that I know more, I would like them to respond with information I have not already tried. Escalation from Customer Support to get the right Technical Support person faster would be nice. Most times, I get a quick response. Sometimes, however, it can take days to get to the person who knows what is wrong or get a fix. Other times, I have solved my issue before they have an answer.

We used Perl and SQL for data integration.

Initial setup was using the Talend Installer, which is very easy but on the next upgrade, we decided to split the systems into individual VMs for better management of security patches. It gets really complex as you go from Data Integration to Data Services Platforms because of the open-source apps in their suite.

I implemented Talend in-house / on-premises. I have no experience with using a Talend vendor for implementing a solution, though this may change in the near future. 

Not sure about the money side but I know it has been easier and less time consuming to complete the same tasks for data integration compared to how we did it prior to using Talend. 

For a production environment, plan to separate the Talend suite of systems onto their own servers for easier management with 'security updates' and secure each one for encryption of data across systems. Using the installer for a Production environment didn't work for what we needed. 

We did evaluate other solutions, although I can't remember the names. They were either more expensive and/or didn't have a community/free version that compared to Talend's Open Studio at the time.

Having developers that are familiar with Java and Tomcat will be very helpful but not required when using Talend.

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.

The scheduling part of the solution is very good.  

Talend has a lot of connectors, which is very useful.

The user interface is good. It's very visual.

The basic tools are easy to pick up and understand.

Some components of the solution are not easy to exploit.

The solution takes quite a long time to master, even with a visual interface. They should work to make it more user-friendly and easier to learn. 

Once you get past the basic tools, it gets pretty complicated.

I've been using the solution for eight months.

I'm a user and a client. I'm a Data Integration Tech.

I'd rate the solution six out of ten.

It's my understanding that the solution is lining up a lot of new features to add and deploy in the near future. That will be great. I hope they continue to focus on new releases.

There are only a few things that are straightforward, however. Many things take a lot of time to understand and get used to. If they can improve the basic stuff, I think it would be much less complicated overall. There are also more connectors that could be added as a feature. Other than that, it's a good product.

This solution is being used on the client-side. It's a data warehouse solution, basically integrating data between Oracle data sources going into a Teradata Database data warehouse.

As far as the features that I have found most valuable, it's fairly easy to understand, even for someone inexperienced going from Informatica and DataStage to Talend. The other positive thing, although I haven't used it personally, is that it shares the same platform as the data quality solution which is important in my line of work. Both sections are beginning to be asked for by our clients. Unlike a few years ago, when it was either you doing a data integration or somebody else doing a data quality assessment, in this day and age they're actually asking for both, and it is a good platform to do both. The other thing about Talend is that it has a lot of push down features, wherein most of the execution that has to be done on the processing side, does not require much heavy lifting up. There's not much need to lift the data so that it can be processed and then pushed back to the database, which was traditionally the approach for the likes of Informatica and even DataStage if they're not using pushdown authentication.

I put Talend on the same playing field as the other platforms and they're very competitive in terms of performance, which is a good selling point. It has very rich features. It provides a very rich feature set in the application.

I don't see any additional need for improvement, at least not in the use cases that I've encountered so far.

I'm not sure if they have it, but including either XML or JSON in the next release would definitely be a good transformation. I'm not sure if Talend has that feature, but it's one of those requirements that we are working around and have to do some parsing of XML so this could make it easier.

I have been working with Talend Data Management Platform over the last year.

Additionally, I've had a few years experience with Informatica, a few years with DataStage, and then a few years with SQL Server, and only recently with Talend.

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.

In terms of scalability, I think from an engineering standpoint, Talend should be able to scale as your database platforms expand, as well. Noting that it has a run-time that basically executes your job on the database side. It should scale fairly consistently with your database growth. I would anticipate that.

I know the support people personally, so yes, I've contacted them for a few inquiries every now and then. None of that too difficult or too serious, it's usually more on unexplored feature sets or specific functionalities that I may have missed the documentation for. It's usually more regarding inquiries rather than solution fixes.

The initial setup is not too simple but I guess somebody out of college would be able to set it up felt fairly easily. So it should be fairly simple.

The Apple deployment took only about a week, but tuning and validation took another two weeks

I observed the implementation, but normally, at least in the projects that I have, we bring in Talend engineers to set up the platform for us.

Deployment was a two-person job. There's a lot of coordination between the system administrators and the database administrators to get the connectors right. It's about a handful of people. Of course, that's not the same as the developers, but for our use case, it was a very small team that deployed it.

Clients are looking for options. Before using Talend, when I was building Informatica and DataStage, they both were the "big bucks" kind of data integration and clients are desperate for deep-dive data warehousing because of the expense. But with Talend, it provides both a quick startup with their community and at the same time, it provides a different financial strategy with their subscription model. There are some clients who are actually financially stable enough and they're looking for a license model or a financial model like what Talend doesn't have. They like its features but it follows a subscription model. So it's even more on the client's business side wherein they want variety, but sometimes the variety is very much limited to the brand.

Basically, like in our case, Informatica and Cappex only offer a staged data payment model. But Talend offers a monthly subscription kind of model, and there are some clients who like the features of Talend, but they are not keen on having an OPEX, an operational expense, kind of financial model.

I would advise potential customers to try Talend's community edition. It would be a good strategy for them to get their hands and feet wet using the community so they'll understand the ins and outs of those sites.

It works well for the product because you get traction in terms of adoption and community. The community is rich enough for people to build actual production solutions, and it's open to expansion in an enterprise community. So that would be a good strategy, especially if a company is still exploring tools. It's a low-cost approach to get started.

On a scale of one to ten, I would rate Talend Data Management Platform a nine. 

What would make it a ten, at least in my region, is the support. In the Philippines, there's only a handful of Talend support. The support is very helpful, but it's very limited. They usually refer you to the community or to their reseller partners, but for direct engineering inquiries, they would have to refer you to their head office. So for a very popular product, their footprint here in the Philippines is still on the development side or ramp-up side.

Support could improve. I'm leveraging it on personal references because I know the people running the show here in the Philippines. But for some of the clients, they would find it difficult to find global support for Talend here in the Philippines.

Extract, Transform, and Load (ETL) transformations are open source and is a valuable feature.

ETL has simplified our integration procedures.

The ETL transformations could be faster.

1 year

no

no

Yes. With K rows it runs fine. With M rows, it runs too slowly and has memory issues.

N/A

N/A

N/A

Somehow straightforward, but could be be less complex.

We implemented with a combination of a vendor team and our own in-house team. The vendor team level of expertise was low.

We haven't calculated our ROI.

The setup cost is high. Day-to-day cost is somewhat medium.

We did not evaluate other options.

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.