Fivetran vs. Relational Junction

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

• 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

• 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

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

• 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