AWS Data Exchange vs. Informatica Cloud Data Integration vs. Layer2 Cloud Connector

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

We use it a lot for importing data. We transform the incoming data to match the formatting of our CRM. We also match on existing records to avoid creating duplicates. Informatica handles all of this exceptionally well. Our users are system administrators. The tool is not well-suited for users who do not have a technical background

Incentivized

We had a scenario where our clients have thousands of external party vendors/committees who regularly sync SharePoint data. Managing thousands of external parties can never be possible without using a Layer2 cloud connector. We managed the local network sharing and SharePoint integration by using the Layer2 connector. Layer2 is convenient with a large amount of data as the per-user license is high.

• 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

• Data synchronisation
• Data replication
• Data integration

• Layer2 provides best connectivity with SharePoint
• It syncs local network shared files to the SharePoint
• Provides details file history

• 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

• There is a moderately steep learning curve
• Has some idiosyncrasies
• Can be finicky with date formats

Incentivized

• Per User cost is expensive
• A lot of pre-requisites
• UI needs to be more user-friendly

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.

There is a learning curve with Informatica. It is not always intuitive to use. It is best suited for technical users such as system administrators

Incentivized

It is really easy to comply and understand its features.

We had also used Microsoft One Drive as a syncing tool but it requires Office365 for managing and syncing data across thousands of vendors which was not practically possible to manage users on Office 365. Layer2 resolved this issue by having 3 user licenses and they are enough to periodically sync all external parties' data with our SharePoint online.

• 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

• Really greatest than any other conventional application.

• Layer2 resolves the time management issue
• Resolved data syncing issues across different external vendors
• LOE optimisation with using Layer2 connector.