Azure Data Factory vs. Azure Synapse Analytics

In a data pipeline, you will be able to add different kinds of activities for example connect from your on-premise SFTP and move CSV files to storage accounts. As well data factory has its own data flow if you are an ETL developer who experimented with maybe you have worked with SSIS, thus, you will start quickly with this new feature of the data factory.

Incentivized

In terms of a well-suited scenario - the Azure Synapse can be used to capture data from multiple sources (especially from onPrem sources apart from Dataverse) and update the transformed data based on the given conditions (eg: refresh data based on the specified date/time ranges). Also, the transformed data can simply be transferred to Azure Data Lake for further processing by utilizing other analytics tools such as PowerBI.

Incentivized

• Creating ETL and ELT workflows as well as orchestrating and monitoring pipelines without writing any code.
• Hybrid data integration is easily and agilely possible through this software.
• It has lot of various useful components

Incentivized

• The combination of SQL/unstructured data
• Keeping things "complicated, but simple"; [heterogeneous] data formats seen as just SQL tables to business experts used to use Power BI, Excel, and any other traditional SQL-oriented BI tools
• Integration options using "Synapse pipelines", the application of ADFs
• The greatly integrated solution of independent things (Spark MPP cluster, MPP SQL Servers, ADFs) - all sitting under one roof. Great job!
• Integration with super-fast, globally replicated data. I really appreciate the integration of NoSQL databases (namely Core API and Mongo API under Cosmos DB) with purely batch-processed BI data

Incentivized

• Learning curve for pipeline creation interface.
• Alerting isn't necessarily built in. Had to work around this to meet team needs.
• With GIT enabled, some features can only be done via git, while some need to be done via the portal.

Incentivized

• With Azure, it's always the same issue, too many moving parts doing similar things with no specialisation. ADF, Fabric Data Factory and Synapse pipeline serve the same purpose. Same goes for Fabric Warehouse and Synapse SQL pools.
• Could do better with serverless workloads considering the competition from databricks and its own fabric warehouse
• Synapse pipelines is a replica of Azure Data Factory with no tight integration with Synapse and to a surprise, with missing features from ADF. Integration of warehouse can be improved with in environment ETl tools

Incentivized

So far product has performed as expected. We were noticing some performance issues, but they were largely Synapse related. This has led to a shift from Synapse to Databricks. Overall this has delayed our analytic platform. Once databricks becomes fully operational, Azure Data Factory will be critical to our environment and future success.

Incentivized

The data warehouse portion is very much like old style on-prem SQL server, so most SQL skills one has mastered carry over easily. Azure Data Factory has an easy drag and drop system which allows quick building of pipelines with minimal coding. The Spark portion is the only really complex portion, but if there's an in-house python expert, then the Spark portion is also quiet useable.

Incentivized

We have not had need to engage with Microsoft much on Azure Data Factory, but they have been responsive and helpful when needed. This being said, we have not had a major emergency or outage requiring their intervention. The score of seven is a representation that they have done well for now, but have not proved out their support for a significant issue

Incentivized

Microsoft does its best to support Synapse. More and more articles are being added to the documentation, providing more useful information on best utilizing its features. The examples provided work well for basic knowledge, but more complex examples should be added to further assist in discovering the vast abilities that the system has.

Incentivized

Azure Data Factory fits well into our overall systems architecture where we already utilize largely Azure services and also Microsoft based products in the on-premises environment. I think cost structure is also very competitive with Azure Data Factory. Most services provide a visual interface for designing ETL workflows, but our team found Azure Data Factory's interface more intuitive.

Incentivized

They're all part of the Microsoft Azure family, so they are not exactly competitors. They overlap in functionality, but they're targeted at different levels of customers. Azure Data Factory is an excellent stand-alone PaaS (included in Synapse Analytics) for writing, scheduling, and monitoring pipelines. Azure SQL Database (and all the Azure SQL family) is excellent for traditional, SQL-based data warehouses, especially if you're migrating from on-premises. Combined with Azure Data Factory (that can run SSIS packages), it's a perfect solution for a simple path to the cloud. Azure Databricks is effectively the only internal "competitor" to Synapse Analytics but targeted more to a "platform-agnostic" audience. On the other hand, Synapse is more of a proprietary mix of products that are more tightly related to Microsoft technologies.

Incentivized

• Limiting the amount of data moving up and down from the cloud for cloud-native applications.
• Overall simple to use interface which is actually easier for a first time ETL developer than SSIS.

Incentivized

• It definitely has a positive impact on ROI. We are able to use it to generate MORE revenue through predictive analytics and pricing optimization.
• Because of the SQL Data Warehouse design, we're able to set up some self service reporting tools which allow our users to generate reports ad hoc instead of having a full time employee creating these by hand.
• Having visibility into the data is very useful for management to make good business decisions.

Incentivized