AWS Data Exchange vs TIBCO Cloud Integration (including BusinessWorks and Scribe)

• 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

Read full review

• Scribe can dependably map or sync data between systems. When you have different systems being used by many departments, this is the tool to keep the data in-sync!
• API's are widely used by many applications and companies. Tibco Cloud Integration allows companies to integrate data from an older ERP system with a newer system using an API.
• Tibco provides the flexibility for business users, developers and anyone in-between to understand where data is moving within their organization.
• One example of flexibility of the solution is easily manipulating data on the fly.

Read full review

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

Read full review

• Missing functionality: We like to run all the files available in the FTP when clicking the run button. Right now, we have to click the run button several times (or have multiple solutions) in order to run files from our FTP site one at a time.
• Generating column fields every time a file changes from the source in the FTP is very tedious. Working in integrations makes me have to go back and forth a lot of the time, and doing this is incredibly annoying.
• The security is horrendous. We installed an on-premise agent on the customer side, but we don't want them even touching the ETL tool at all. The only knowledge we are fine with knowing and being able to see is that they installed the agent, not the solutions themselves.
• Our company's connector would have to point to the dataset name rather than dataset ID. It was very frustrating because we change the dataset name a lot, and then we'd have to repoint it.
• It's very difficult to monitor the different integrations that go on because there isn't a consolidated dashboard.

Read full review

• 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%

Read full review

• The data migration has been extremely slow. Things that should have taken a short amount of time have gone way past where any of us though.
• Job monitoring has been more resource intensive and time consuming that planned for.
• Researching and searching for things is time consuming.
• There is no way to easily organize solutions. So there are hundreds of solutions in the list with no easy way to put them in folders or something like that. The only thing you can do is name them specifically so that you can filter them. But filtering is not very good in Scribe.
• The concept of Scribe is good. I like the graphical flow builds in the maps. It just doesn't work very well yet. maybe as they improve it.

Read full review