AWS Data Exchange vs. Fivetran vs. Striim

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

Fivetran's business model justifies the use-case where we require data from a single source basically a lot of data but if the requirement is not on the heavier side, Fivetran comes to costly operation when compared to its peers. Otherwise, I'll recommend Fivetran for stability and update and seamless service provider.

Incentivized

Below samples are the well suited use cases; - Change data capture feature seamlessly works on popular RDMS. You can make enrichments on several data sources within the same Striim application. - You can install stand alone agents and start streaming log files to Striim servers. This is mainly useful for security operations or audit trail use cases.

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

• Easily connects to source data using delivered connectors
• Transforms data into standard models and schemas
• Has very good documentation to help quickly setup connectors

Incentivized

• GoldenGate Trail reader which iss faster than Oracle CDC. It does not used logminer, hence there is no load on source Oracle database.
• Easy installation and upgrade in 5 minutes
• Support is very good. Fast and user friendly.

• 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

• Very difficult to get connectors enhanced if a specific needed object is not supported by them
• Depending on the edition needed and the data volumes, can get quite expensive

Incentivized

• License a bit expensive

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.

Very easy and intuitive to setup and maintain as there usually are not that many options. Very well documented (e.g. how to setup each connector, how the schema looks like, any specific features of this connector etc.). Also the operation is intuitive, e.g. you have status pages, log pages, configuration pages etc. for each connector.

Incentivized

It runs pretty well and gets our data from point A to point cluster quickly enough. Honestly, it's not something I think about unless it breaks and that's pretty rare.

Incentivized

We never seriously considered using anything else. Our data engineers had used Fivetran extensively in previous roles so when it came time to make a decision, there wasn't much of a process. They gladly signed the contract with Fivetran pretty quickly.

Incentivized

Faster, checkpointing better. CDC works well. The loading is faster. Easy upgrade and installation. Uses less resource.

• 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 has been very positive in serving BI team with new source requests
• It has been OK at scaling to match as data volumes as source data size grows

Incentivized

• We got the license at a discount price