Layer2 Cloud Connector vs. Talend Data Integration

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.

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

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

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

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

• 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

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

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.

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

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

• 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