Qlik Talend Cloud Reviews

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.

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.

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.

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.

Talend is an ETL solution. It is great for moving data from source to target and has great error-handling and capturing techniques. Talend is easily becoming more recognized within the ETL space. I am seeing more and more companies branching out from the Oracles of the world since cloud was introduced. Cloud has seemed to even the playing field a bit. If you are looking for something that is stable, cost-effective and has a great ROI, then Talend is a great choice. I have compared ODI to other tools in reviews in the past, but I haven't compared it with Talend.

Implementing Talend can easily speed up implementation time and reduce the amount spent on the learning curve. Talend reminds me of a tool I used years ago called Hyperion Application Link (HAL). If you had basic knowledge of integration, you could pick up this tool in no time flat. The big difference between HAL and Talend is that the processing abilities of Talend are much better. HAL is clunky and slow. Talend is a powerhouse of ETL.

I love the fact that I can copy a step, click a button, and now I have the opportunity to create the opposite of what I was doing. 

For example: If I am creating an inner join which produces a file on the target, there could be records that do not have a match. In other ETL tools, you would have to create a whole different process. In Talend, all you have to do is copy the inner join, and there is an option for rejects. Now you can create a separate file for your business users to review.

There are no natural connections for some of the applications that I use more regularly. I think that if Talend wants to disrupt the market a bit, they could create built-in calls to Oracle Hyperion applications. 

As far as the next release, I would like to see connections to SAP work a bit better. They have a little lag, but this is just me reaching for something because they asked.

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

This can be a full data warehouse solution at the enterprise level.

We never really had to use it before and never really had a big issue. We only had smaller issues when we first started using it. Talend was very responsive and helpful.

My solutions are client dependent. I do help them evaluate which tool they should use in some cases, but I can't say "I had this tool and I switched because of XYZ".

It's very simple to install. So easy a caveman can do it? No, but someone with basic knowledge of databases can easily get this going.

As a consultant, I do the implementations myself, or a member of the team completes the implementation.

No vendor teams were harmed in the making of our projects.

The ROI on this tool varies. I would say that with the ease of use, you could easily get your worth out of the tool in the first few months.

Make sure you wait until the end of the quarter to get the best deal. Try to talk to multiple salespeople, and sometimes you can get multiple discounts. Let me know, and I can help.

My solutions are client dependent. I do help them evaluate which tool they should use in some cases, but I can't say "I had this tool and I switched because of XYZ".

Just be careful to think through everything that you want to do. There are reusable parts to Talend. Use the variables properly. This is advice for any ETL solution.

We have a legacy system (Wins + DB2), which stores all our data.

For reporting purposes (from SQL), we need to analyze data. We use it for making decisions, for example, if we want to display data elements in our reports based on if a column ever gets a value entered by user or what are distinct values that we are receiving for transformation purposes.

We use it to check patterns, like zip code, state codes, and phone numbers.

We also check data value frequency for business decision in mapping from one system to another.

With its frequency function, we were able to pick a line of business to be addressed first in one of our conversion projects.

We have used value frequency and patterns. We have been it impressed with these functions as they have helped us in making decisions in transformation work.

• Displaying columns, which are not part of join, in redundancy analysis.
• You can't join more than two tables for analysis.
• SQL for displaying underlying data in non-match results does not work.

In redundancy analysis, the query is failing to bring non-matched records. This query is an internal script. There is no way (that I know of) to fix this syntax error for future runs.

We have not worked extensively on this tool to comment on its scalability.

We have not used technical support for DQ.

We were using an SQL and Excel combination.

We found the Portal installation straightforward. However, it stopped working one day and we still cannot bring it back up and running, even with a reinstall.

We did not purchase a separate license for DQ. It is part of our data platform suite, and I believe it is well-priced.

No. But we use Talend DI and ESB so wanted to explore this feature as well.

The Studio is easy to understand. The analysis and reports are easy to build as well. We have been using it for the past four to six months now. We do not have many analyses created though. Since our Portal is not working, we are not using it to its full potential, which I want us to use. Therefore, this product has room for improvement. 

• Fixing data by using regular expressions or synonyms and Data Stewardship.
• Using data profiling to gauge the quality of the data before and after it’s used/needed.
• Master Data Management - Authoring and matching survivorship, including Data Stewardship.

It allows our customers to master and expand their products to an international scale. In addition, it enables customers to consolidate multiple, disparate sources of data into a centralized, master data hub which can used for operations or analytics.

The solution enables robust data matching, merging, survivorship, and Data Stewardship that can be a part of data quality workflows or true master data management.

Needs integrated data governance in terms of dictionaries, glossaries, data lineage, and impact analysis. It also needs operationalization of meta data.

We’ve created an MDM-like system. The MDM hub is built on an Oracle Database. The system is retrieving data from different sources like files, a Microsoft SQL Server and Oracle DB. The data is being processed by our cleansing process. We’re using Talend DQ components, web services, and custom Java code to clean our data. Once the data is cleansed, we load it into the MDM hub where the records are matched and consolidated. The consolidated records are then written back to specific target sources.

It’s easy to monitor the processes. Every morning I’ll open the Talend Administration Center to check the status of the process. Within seconds I’m able to see which process ran successfully and which have failed and why they failed.

We’re also able to respond much more quickly to changes and demands from the business. We can create and change jobs quickly. When the business wants new data for a report, we can provide the data within hours.

The jobs are visual and this has improved collaboration between colleagues. It’s much easier to understand a visual job than a piece of Java code.

The numerous components provided by Talend. With these components you’re able to create jobs quickly and efficiently.

I also really like the fact that there are no out-of-the-box solutions regarding the development of jobs. Other vendors may have modules which cleanse your addresses. In Talend, you have the freedom to completely develop the process yourself. This can be tricky, but it also makes it fun.

When we upgraded to Version 6.4.1, we tried using a GIT repository instead of a SVN repository. After a few incidents where things disappeared and changes were not saved, we decided to go back to a SVN repository.

Never had any real issues with the Talend server applications. The only issues we had were related to the limited resources of our development and test environments. Nothing a restart couldn’t fix.

If we encounter issues, it’s most likely when using the Talend Open Studio. The studio can be slow, get stuck, or crash. But again, it can be caused by the resources of your machine or your connection with the repository. If we encounter issues with the Studio we restart the Studio. In emergencies, we create and use a new workspace.

All my projects have been relatively small. I have never needed to scale.

My experiences with support have been quite good. I’ve never had issues which weren’t resolved, or where I had the feeling that they didn’t have the knowledge to help me. Depending on the location of the support engineer, it can be a bit difficult to communicate.

I’ve never used another solution.

Talend provides an installer which makes the installation straightforward.

If you want to tweak the installation you’ll need some knowledge of the different third-party applications like Tomcat, Elasticsearch, Kafka, etc. Some of the tweaks are documented in the Installation guide.

I have never had to deal with pricing and licensing. But I would advise to first take a look and at the Open Studio edition. Figure out what you need and purchase the appropriate license.

My company had already partnered with Talend before I started. We’re also using Informatica and we’re looking into Human Inference.

Keep your jobs small and simple, split large jobs into multiple smaller jobs. One of the major pitfalls is creating one huge job which does everything. This is detrimental for the performance of the job. It also makes it harder to read and understand the job, let alone debug the job.

Always use metadata and contexts groups. Deploying will be a lot easier.

Use the documentation possibilities in your jobs. Name the component, data flow, and sub jobs. This will increase the readability of the jobs.

I would give it an eight out of 10. In the last four years I have seen the product grow and improve but there is still more room for improvement.