Apache Flink vs. Qlik Talend Cloud vs. Talend Open Studio (discontinued)

In well-suited scenarios, I would recommend using Apache Flink when you need to perform real-time analytics on streaming data, such as monitoring user activities, analyzing IoT device data, or processing financial transactions in real-time. It is also a good choice in scenarios where fault tolerance and consistency are crucial. I would not recommend it for simple batch processing pipelines or for teams that aren't experienced, as it might be overkill, and the steep learning curve may not justify the investment.

Incentivized

The same way you design data integration job can be used to design services. It is easy to enhance by custom components and can adapt to all requirements. Talend Data Integration connects to [a] multitude of data sources and streaming service. Very easy interface to design complex applications without spending much time on coding. Easy to learn and master. Talend constantly strives to better itself by adding more features and functionalities.

It is certainly suitable for agile and innovative projects. For developments that require particular steps and with a simple debug. On the other hand, it is not very suitable for producing flows that move large amounts of data and that require a lot of resources and great stability.

Incentivized

• Low latency Stream Processing, enabling real-time analytics
• Scalability, due its great parallel capabilities
• Stateful Processing, providing several built-in fault tolerance systems
• Flexibility, supporting both batch and stream processing

Incentivized

• We used Talend to ETLing the data from myriad sources such Oracle Database, Clarify, Salesforce, Sugar CRM, SQL DB, MQ, Stibo Step, FTP, Netezza, and Files.
• We leverage Talend transformation capabilities for stitching the data , unions and join
• We successfully created the final unified set that can be used by business

Incentivized

• It does provide a lot of predefined functionality out of the box along with providing the facility to use complex java code for developers.
• Mainly like it for small data utilities. It does provide a lot of control for developers.
• Pricing is, of course, a major plus :)

Incentivized

• Python/SQL API, since both are relatively new, still misses a few features in comparison with the Java/Scala option
• Steep Learning Curve, it's documentation could be improved to something more user-friendly, and it could also discuss more theoretical concepts than just coding
• Community smaller than other frameworks

Incentivized

• Pricing for sure can be the area for improvement.
• Real time processing is slow as compared to other tools like Abinitio.
• While developing batches, it crashes a lot. It may be the issue with me, but I wanted to highlight it.

Incentivized

• The community is not that up to date and forum is not that great in response. Probably we should make people aware of the tool more on how to use and its implementations.
• Talend crashes when transforming a lot of data (millions of rows).
• Proper training documentation is a must for talend which is currently lagging. This will help users to learn more about Talend and use it effectively.

Incentivized

There is no licence requirement for Talend Open Studio. So, this is not relevant question. However, if you are asking whether we will use Talend in future. Yes. We will continue to use it. It's very powerful free tool which caters to all our extra, transform, load capabilities. We just love Talend for it's great functionality and ease of use.

Incentivized

We use Talend Data Integration day in and day out. It is the best and easiest tool to jump on to and use. We can build a basic integration super-fast. We could build basic integrations as fast as within the hour. It is also easy to build transformations and use Java to perform some operations.

Incentivized

Talend Open Studio is based on Eclipse and is full of redundant procedures to do one thing, like when installing libraries. Sometimes I cannot manually download the libraries that it can't find.

Many times, Talend freezes. When you give a cancel command, it takes several minutes to stop. It also takes a great toll on our PC with 16 GB of ram and I7 CPU, even in idle status. If you are downloading Maven Jar/Libraries, you cannot do anything and have to wait until the task is finished.

Good support, specially when it relates to PROD environment. The support team has access to the product development team. Things are internally escalated to development team if there is a bug encountered. This helps the customer to get quick fix or patch designed for problem exceptions. I have also seen support showing their willingness to help develop custom connector for a newly available cloud based big data solution

Incentivized

There is only one support staff on a forum created by Talend, which hides behind a nickname and does not show his name. They only ask base questions like: -Talend version - Are you in a proxy? -Do you have all the libraries installed? -It is a Jar missing? (how could I know?) -Follow this link on our site or "please ask your administrators" They then wash their hands of my issues.

Apache Spark is more user-friendly and features higher-level APIs. However, it was initially built for batch processing and only more recently gained streaming capabilities. In contrast, Apache Flink processes streaming data natively. Therefore, in terms of low latency and fault tolerance, Apache Flink takes the lead. However, Spark has a larger community and a decidedly lower learning curve.

Incentivized

Talend has many built-in components that reduce the development work. We were able to complete the project sooner than expected. Easy to on-board resources as it is straightforward to use. We can manage all the pipelines in the cloud with simple alerting. No major downtimes. Connectors to all new applications in the market.

Incentivized

Informatica has a limited number of components that you can use. This places a heavy limitation on the capabilities of Informatica. On the other hand, Talend allows you to create your own custom components using Java. For businesses that need to perform a wide variety of data operations, it can be quite useful to have the option of creating your own custom components to satisfy business needs.

Incentivized

• Allowed for real-time data recovery, adding significant value to the busines
• Enabled us to create new internal tools that we couldn't find in the market, becoming a strategic asset for the business
• Enhanced the overall technical capability of the team

Incentivized

• It’s only been a positive RoI with Talend given we’ve interfaced large datasets between critical on-Prem and cloud-native apps to efficiently run our business operations.
• 40K+ plots data, covering 1K+ crop varieties.
• 3K+ Customer & their credit data, 3K+ product inventory & pricing.

Incentivized

• Being Open Source, your costs on the IDE side are zero.
• There are a lot of programmers with knowledge in Eclipse, they will be comfy using TOS. The development process will be faster.
• Once you develop your Service Bus using TOS, you can connect easily with other Talend products, like DTS, Big Data analysis tools, etc.

Incentivized