Qlik Talend Cloud

My main use case for Qlik Talend Cloud  is often for creating REST services, SOAP services, and rarely for doing ETL.

Let's say we want to launch a project where the client has to go through a menu with options, then enter the amount, then enter the recipient's number for the credit or the bundle. On our side, we create a service that we expose and can call, for example, 'purchase bundle.' This 'purchase bundle' service will take as input the bundle ID and the recipient's number as a GET service. In the service flow, it will be a REST service which in the flow will first call a backend to check whether the initiator has sufficient credit, then a second backend to check whether the sender's number is a valid number, then a third backend to check whether this product is a valid product. After all these checks, it then gives the product to the recipient and returns a response. Since it's a GET service, the response could be in XML or JSON. In that response, there will be a 200 status code. Then, in the payload of the response, it will depend on what we want to give. We can for example put 'successful,' 'the request was processed successfully,' or just put 'OK.' In any case, it will be something where, when you see it, you'll know that this is a success.

Generally, that's it. I gave you a practical case. There are many cases and several cases, but in all cases, it revolves around REST or SOAP services.

In my opinion, the best features that Qlik Talend Cloud  offers are excellent for me within the scope of my use, as I use it to create REST and SOAP services. For me, that's excellent and top-notch. I've been using it for 7 years and haven't switched to use another technology. That means it's fine. The fact that we also do drag and drop is great and works well. Another thing is the fact that it offers the possibility to create routines. If you want to do something that doesn't exist as a component, then you can even create it yourself as a routine with Java code. I use Java as a routine to do whatever I want and integrate it into my flow. That too is great.

The features of drag and drop make my daily work easier by providing speed of execution. Regarding the flow, it also allows readability. As for creating routines, I had a case where what I wanted to do did not have a component to do it, so I created a routine. I still stay on Qlik Talend Cloud because today, if this platform were limited only to components and drag and drop, and if I had another service that I wanted and these components didn't allow for it, then I would have left Qlik Talend Cloud to use another platform. But fortunately, whatever I want to do, I can stay on Qlik Talend Cloud to do it there.

Before, when we wanted solutions and REST APIs, we handed it over to an external company, so it took time, back and forth and all that. Now, when we got Qlik Talend Cloud, when we want a service, we create it. In at most one or two days, the service is in production and usable. So we save a lot of time.

Let's say that if before it took us 10 days to create a service, deploy it in production and all that, today it takes us 3 days. So we save 7 days, which is a 70% saving.

In terms of benefits, I would say that I see savings and time gain. Time gain, I talked about it when I gave the example of creating an API, what it took us and so on. As for savings as well, we can talk about that because before, if you gave all the applications and services work to an external integrator, indeed, managing it in-house allows you to save money.

I would really like today, since we're talking about AI, to be able to integrate it into Qlik Talend Cloud studio, so that we can explain the flow or describe the flow and then it creates it.

Knowing that my team works based on documentation provided by the architects, that means we will define a specific type of documentation for Qlik Talend Cloud, so that as soon as the architect provides the documentation, we—whether it's, for example, a chat window in the studio—as soon as we copy and paste the documentation with all the possible details, the URLs of the backends, the IPs of the databases, the table names and all that, and if we normally have all the details, the creation could be very easy. Since we have experience with Qlik Talend Cloud, we know exactly how to use the components.

The only risk is that you will have to test the flow properly and do a thorough review. That's it. It's not exactly a risk, but since I know it's a risk, that means I'll anticipate it.

In my experience, Qlik Talend Cloud is stable if it's properly sized. You have to size it properly. You need to know the load you're going to receive and adapt it.

Regarding scaling, since we have Qlik Talend Cloud on-premises, it adapts based on increasing volumes or needs.

In any case, on-premises, we have to manage it manually. We've set up alerts, so if we have an increasing volume and so on, it's up to us to increase CPU, increase RAM, and all those details.

Regarding Qlik Talend Cloud's customer support, it's fine.

Often, when you need help, you open a ticket. Then they ask you for the logs and all that, you give them the logs, they troubleshoot. Sometimes, if it takes time, you ask for a live session, that is a live troubleshooting session, you share your screen and you go through it together.

We weren't using one before; we just outsourced. So Qlik Talend Cloud is the first integration solution we use.

I would say we just prepared ourselves because before, we did a benchmark. We just prepared ourselves. There's not too much impact, since it was already planned.

In terms of benefits, I would say that I see savings and time gain. Time gain, I talked about it when I gave the example of creating an API, what it took us and so on. As for savings as well, we can talk about that because before, if you gave all the applications and services work to an external integrator, indeed, managing it in-house allows you to save money.

The setup cost is very expensive.

I looked at Oracle's OSB and Qlik Talend Cloud.

I chose Qlik Talend Cloud rather than another solution because there are advantages regarding the ease of use and the cost. On the cost side, it's cheaper.

My advice for a company that is considering using Qlik Talend Cloud is that they need to know the load, size it properly, and also train the developers properly, because some components are more optimized than others, and the rest will follow. I would rate this product as an 8 overall.

My main use case for Qlik Talend Cloud  involves using it for data integrations and ETL, ELT pipelines to support our data warehouse and analytics platforms.

A specific example of how I use Qlik Talend Cloud  for data integration involves working on several data engineering projects across different industries, with a main focus on data integration, analytics, and cloud. In designing and implementing a complete data warehouse, I integrate multiple data sources such as ERP , e-commerce platforms, and external APIs. In this role, I use Talend extensively to build and manage ETL pipelines, improve performance, and ensure data consistency for BI tools such as Power BI and Grafana . Before that, at Accenture, I worked on large strategy and international projects, supporting and modernizing data platforms for global clients. My experience covers the full data lifecycle, from understanding business requirements and designing the architecture to developing, deploying, and maintaining outstanding data products and great data pipelines.

I want to add that we use Qlik Talend Cloud not just as an ETL tool, but as part of a broader data architecture. I rely on it to create reliable, reusable, and well-governed pipelines, especially in environments where data comes from many sources and needs to be delivered consistently to analytics teams. I pay a lot of attention to performance tuning, job design, and monitoring so pipelines are stable and easy to maintain. I also use Qlik Talend Cloud in standard data models, enforce data quality rules, and support incremental and near-real-time loads when needed. This helps ensure the downstream systems such as data warehouses, dashboards, and compliance reports always receive accurate and trusted data. Overall, Qlik Talend Cloud plays a key role in helping me deliver scalable, production-ready data solutions that align technical implementation with business needs.

The best features of Qlik Talend Cloud are its connectors to many systems, databases, APIs, and files, including both SQL and NoSQL databases. The scheduling feature allows me to run jobs automatically in the cloud, and the built-in data quality tools help clean and check data. The reusable components enable me to reuse jobs and parts, which saves time, making it easy to build good data pipelines.

The feature that has made the biggest difference for me in Qlik Talend Cloud is the scheduling and automation, which helps me run ETL jobs automatically without manual work. This saves time, reduces errors, and makes the pipelines more stable. In my daily work, I can trust that the data is updated on time and ready for reports and analytics.

Qlik Talend Cloud has had a positive impact on my organization by automating data integration processes, reducing manual errors, and ensuring reliable and up-to-date data for reports and business decisions. This has improved operational stability, productivity, and trust in the data.

Since using Qlik Talend Cloud, we have reduced manual work, resulting in approximately 20% to 30% time savings in data load processes. We have also seen a reduction in operational errors, mainly due to automation and the data quality checks, and a clear improvement in data reliability since the pipelines became more standardized and monitored.

Qlik Talend Cloud could be improved with more advanced monitoring and flexible alerts, as well as better job performance visibility.

It would also help to have a better job version and comparison experience to support team collaborations. Additionally, having more detailed error messages and easier job debugging would be beneficial. Better cost and resource visibility would also help teams optimize their workloads.

I have been using Qlik Talend Cloud for 10 years.

Qlik Talend Cloud has not presented any stability issues.

Its scalability is good, as Qlik Talend Cloud can handle large amounts of data and grow as needed, especially in cloud environments.

The customer support for Qlik Talend Cloud is good.

We have seen a return on investment with Qlik Talend Cloud. We achieved around 20% to 30% time savings in the ETL process, reduced operational errors, and improved pipeline stability, allowing my team to focus on analytics work without needing to increase headcount.

My advice to others looking into using Qlik Talend Cloud is to start with simple use cases, use automation and scheduling, and define standards early. This helps deliver value quickly and keep pipelines stable and easy to maintain. I would rate this product an 8 out of 10.

My main use case for Qlik Talend Cloud  involves extracting data from different sources and loading it to the target database by applying various transformation rules that I receive from the business.

In a specific project, my role involves extracting data from SAP systems and different databases, applying the transformation rules received from the business, and loading it to target database systems, which could include anything from files to databases. After the data is loaded, I perform some unit testing and load the job into Qlik Talend Cloud .

Regarding my main use case with Qlik Talend Cloud, I feel that compared to other ETL tools, Talend is better because it is built on Java; this allows users to customize their own requirements and logic. It is very easy to use and offers multiple connectors and components, with around 900 plus components available.

The best features Qlik Talend Cloud offers include the fact that it is built on Java, which gives me the chance to customize my requirements and write my own Java code to achieve my logic.

Qlik Talend Cloud has impacted my organization by increasing the license cost, leading many companies to decide to decommission Talend, as they find the cost too high.

To improve Qlik Talend Cloud, I think the license cost should be reduced, and it should collaborate with multiple companies like Salesforce  to enhance its performance.

I have been working in my current field for around eight years.

Qlik Talend Cloud is very stable.

The scalability of Qlik Talend Cloud is up to the mark.

The customer support for Qlik Talend Cloud is very good.

My experience with pricing, setup cost, and licensing is rated as one.

I rated my experience with pricing, setup cost, and licensing as one because the license cost has increased significantly, leading many companies to seek more profitable options in the market.

As companies decide to decommission Talend due to the license cost, my team has migrated all the Talend ETL jobs to Java,  Spring  Boot, and Spark, resulting in many Talend developers leaving the project since there is no work for them to do.

My advice for others looking into using Qlik Talend Cloud is to consider shifting to other cloud technologies like  Azure  Data Factory or AWS , as there are multiple ETL tools available that they can switch to. I have rated this review as a 7.