AWS Data Exchange vs. Qlik Talend Cloud

AWS Data Exchange fits best for scenarios where you have datasets that you would like to sell and you want to deliver it to anyone who would like to purchase it. It really beats having to set up downloads via your own website or portal. However, it can get complicated to manage if you're trying to deliver a dataset a client has already paid for.

Incentivized

This tool fits all kinds of organizations and helps to integrate data between many applications. We can use this tool as data integration is a key feature for all organizations. It is also available in the cloud, which makes the integration more seamless. The firm can opt for the required tools when there are no data integration needs.

Incentivized

• Simplified data delivery
• Ability to create any amount of data products
• Ability to integrate payment plans with data products
• Tracking data downloads and users
• Integration with other AWS data services

Incentivized

• Talend Data Integration allows us to quickly build data integrations without a tremendous amount of custom coding (some Java and JavaScript knowledge is still required).
• I like the UI and it's very intuitive. Jobs are visual, allowing the team members to see the flow of the data, without having to read through the Java code that is generated.
• Dynamically table creation from new source.

• Integration with more data sources
• Ability to deliver data to clients without AWS accounts
• Inclusion of direct data downloads in addition to asynchronous methods

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

There have been a lot of problems with ADX. First, the entire system is incredibly clunky from beginning to end.First, by AWS's own admission they're missing a lot of "tablestakes functionality" like the ability to see who is coming to your pages, more flexibility to edit and update your listings, the ability to create a storefront or catalog that actually tries to sell your products. All-in-all you're flying completely blind with AWS. In our convos with other sellers we strongly believe very little organic traffic is flowing through the AWS exchange. For the headache, it's not worth the time or the effort. It's very difficult to market or sell your products.We've also had a number of simple UX bugs where they just don't accurately reflect the attributes of your product. For instance for an S3 bucket they had "+metered costs" displayed to one of our buyers in the price. This of course caused a lot of confusion. They also misrepresented the historical revisions that were available in our product sets because of another UX bug. It's difficult to know what other things in the UX are also broken and incongruent.We also did have a purchase, but the seller is completely at their whim at providing you fake emails, fake company names, fake use cases because AWS hasn't thought through simple workflows like "why even have subscription confirmation if I can fake literally everything about a subscription request." So as a result we're now in an endless, timewasting, unhelpful thread with AWS support trying to get payment. They're confused of what to do and we feel completely lost.Lastly, the AWS team has been abysmal in addressing our concerns. Conversations with them result in a laundry list of excuses of why simple functionalities are so hard (including just having accurate documentation). It was a very frustrating and unproductive call. Our objective of our call was to help us see that ADX is a well-resourced and well-visioned product. Ultimately they couldn't clearly articulate who they built the exchange for both on the seller side and the buyer side.Don't waste your time. This is at best a very foggy experiment. Look at other sellers, they have a lot of free pages to try to get attention, but then have smart tactics to divert transactions away from the ADX. Ultimately, smart move. Why give 8-10% of your cut to a product that is basically bare-bones infrastructure.

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

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

In comparison with the other ETLs I used, Talend is more flexible than Data Services (where you cannot create complex commands). It is similar to Datastage speaking about commands and interfaces. It is more user-friendly than ODI, which has a metadata point of view on its own, while Talend is more classic. It has both on-prem and cloud approaches, while Matillion is only cloud-based.

Incentivized

• Reduced time to publish datasets for sale by more than 80%
• Increased net profit from dataset sales by ~10%
• Reduced data delivery time to clients by 15%

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