We performed a comparison between Azure Data Factory and Microsoft Azure Synapse Analytics based on our users’ reviews in four categories. After reading all of the collected data, you can find our conclusion below.
Comparison Results: Both of these solutions are very dynamic, robust, stable, and very flexible. As they are both part of the Microsoft Azure ecosystem, they are both very popular and highly regarded. Many of our users feel Azure Data Factory is an easier solution to understand and get started with out of the box. Microsoft Azure Synapse Analytics is more diverse and works better with a varied amount of different areas and industries.
"The most valuable features of Azure Data Factory are the flexibility, ability to move data at scale, and the integrations with different Azure components."
"The initial setup is very quick and easy."
"The most valuable feature of this solution would be ease of use."
"From what we have seen so far, the solution seems very stable."
"The flexibility that Azure Data Factory offers is great."
"We haven't had any issues connecting it to other products."
"When it comes to our business requirements, this solution has worked well for us. However, we have not stretched it to the limit."
"The workflow automation features in GitLab, particularly its low code/no code approach, are highly beneficial for accelerating development speed. This feature allows for quick creation of pipelines and offers customization options for integration needs, making it versatile for various use cases. GitLab supports a wide range of connectors, catering to a majority of integration needs. Azure Data Factory's virtual enterprise and monitoring capabilities, the visual interface of GitLab makes it user-friendly and easy to teach, facilitating adoption within teams. While the monitoring capabilities are sufficient out of the box, they may not be as comprehensive as dedicated enterprise monitoring tools. GitLab's monitoring features are manageable for production use, with the option to integrate log analytics or create custom dashboards if needed. The data flow feature in Azure Data Factory within GitLab is valuable for data transformation tasks, especially for those who may not have expertise in writing complex code. It simplifies the process of data manipulation and is particularly useful for individuals unfamiliar with Spark coding. While there could be improvements for more flexibility, overall, the data flow feature effectively accomplishes its purpose within GitLab's ecosystem."
"The setup is pretty simple."
"The solution's scalability is very, very good. It's one of the most important aspects for us."
"The solution operates like a typical SQL Server environment so there is no alienation in terms of technical knowledge."
"The architecture, including compute and storage, is good."
"The solution can scale."
"The most valuable feature of Microsoft Azure Synapse Analytics is the pipeline that is the ETL tool. It's very well designed and is overall very good. We usually don't use the ETL tool in Databricks, but we use the ETL tool in this solution."
"It is a fantastic product; we are satisfied with its features and performance."
"Synapse Analytics' best feature is its ability to process large files."
"Data Factory's performance during heavy data processing isn't great."
"There are limitations when processing more than one GD file."
"There's space for improvement in the development process of the data pipelines."
"The setup and configuration process could be simplified."
"One area for improvement is documentation. At present, there isn't enough documentation on how to use Azure Data Factory in certain conditions. It would be good to have documentation on the various use cases."
"There should be a way that it can do switches, so if at any point in time I want to do some hybrid mode of making any data collections or ingestions, I can just click on a button."
"You cannot use a custom data delimiter, which means that you have problems receiving data in certain formats."
"We are too early into the entire cycle for us to really comment on what problems we face. We're mostly using it for transformations, like ETL tasks. I think we are comfortable with the facts or the facts setting. But for other parts, it is too early to comment on."
"Comes with a pretty steep learning curve."
"We'd, of course, always like to pay less for the service if we can."
"An area for improvement in Microsoft Azure Synapse Analytics is its user interface. You can use it for analytical purposes, but its platform should be a little bit more user-friendly. Another small point for improvement in Microsoft Azure Synapse Analytics is its stability. It's good currently, but it could still be improved. Microsoft is combining different tools and technologies into one solution, so in the future, I'm expecting to see even more improvement in Microsoft Azure Synapse Analytics. An additional feature I'd like to see in the next version of Microsoft Azure Synapse Analytics is the drag-and-drop feature. If you're doing some integrations where you can write Scala or you have SPARK programming or SQL, or you're combining different programming, the process should be seamless, and you should be able to drag and drop in Microsoft Azure Synapse Analytics. When doing reporting in the solution, you should also be able to drag and drop. There should be connectors available and a drag-and-drop feature available in the user interface of Microsoft Azure Synapse Analytics, so you won't have to worry about how all processes would work together. You need to be able to drag and drop even from the backend, and having this feature will make the solution more user-friendly."
"Documentation could be improved."
"I am pretty sure that there are areas that need improvement but I just can think of them off the top of my head."
"It could be beneficial to focus on integration with various data sources and similar enhancements."
"Microsoft Azure Synapse Analytics's pricing could be reduced."
"The product could be more feature-rich."
More Microsoft Azure Synapse Analytics Pricing and Cost Advice →
Azure Data Factory is ranked 3rd in Cloud Data Warehouse with 81 reviews while Microsoft Azure Synapse Analytics is ranked 2nd in Cloud Data Warehouse with 86 reviews. Azure Data Factory is rated 8.0, while Microsoft Azure Synapse Analytics is rated 7.8. The top reviewer of Azure Data Factory writes "The data factory agent is quite good but pricing needs to be more transparent". On the other hand, the top reviewer of Microsoft Azure Synapse Analytics writes "No competitors provide the entire solution to one place ". Azure Data Factory is most compared with Informatica PowerCenter, Informatica Cloud Data Integration, Alteryx Designer, Snowflake and Oracle Data Integrator (ODI), whereas Microsoft Azure Synapse Analytics is most compared with SAP BW4HANA, Snowflake, Oracle Autonomous Data Warehouse, Teradata and Amazon Redshift. See our Azure Data Factory vs. Microsoft Azure Synapse Analytics report.
See our list of best Cloud Data Warehouse vendors.
We monitor all Cloud Data Warehouse reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.
I know you're looking for someone who's done research for you but realize that's actually something people get paid to do.
That said, what you're asking about is a mix of quite different tools when you throw KNIME in the mix. I don't know that tool but sounds like its for specific purpose and it's not an Azure tool. Realize there's endless ETL tools out there. I've used about 1/2 dozen in my career. I currently use both ADF and SSIS. I only use ADF when I have to as it's overly complicated to do version management and deal with ARM templates and is very very slow in comparison to SSIS. ADF can however be a good orchestrator for running SSIS - there's an Azure/PaaS version of SSIS called SSIS-IR that can run from ADF. Synapse Analytics pipelines which is actually ADF technology but stripped down. And now there's Fabric Data Factory which is again ADF but even more stripped down. Fabric is also bleeding edge.
ADF has been around for long time now. Anything Azure is cloud based and integrates with Azure services. KNIME is not that. I advise first on understanding fundamental requirements such as, what are the skill levels of your staff with ETL? Are you an Azure shop? What kind of data volumes are you talking about? What sources do you need to connect to (that's a biggy because not all tools talk to all sources!) What are you trying to do - build a datamart or EDW or just copy some data from a source or ? Do you use PowerBI? These will help drive what kind of tool you're looking for. If you want SAAS like as possible tool due to minimal requirements, low data volumes and low staff expertise and starting from scratch, I'd give Fabric a try especially if you want low tech and already into the Power platform. Hope that helps
I believe Synapse is not an ETL tool. ADF is one optional ETL tool for a Synapse Data warehouse.. What Are the Top ETL Tools for Azure Data Warehouse? | Integrate.io
I'd like to step back and pose a bigger option. You see, ETL means making a copy of data you have already. Have you considered a data fabric or mesh, where the data is used where it lies now? Consider this if your data is already used by some systems, but you need to do a more comprehensive analysis of it.
I always want to reduce the replication of databases. The concept of build yet another database to "replace" all the others rarely works out that way. I'd rather beef up the origination system, or use a replica than build a huge portfolio of ETL programs and an army of ops, data governance, and system support to keep them in sync.
Finally, if you really need an ETL tool, i.e. copies of all that data... look for existing talent in your staff. Otherwise, expect to hire some people experienced with the new tool that can advise on design and development and mentor existing staff.
A couple of questions before starting the feature comparison: i. Are you fine with an open-source solution? ii. Any specific reason you have listed ADF? iii. Who will be using these tools and how much learning curve is involved within the team? iv. What kind of data you are dealing with? v. Is data privacy an important factor? vi. Are you looking for only a cloud-based solution or open to a hybrid solution also? vii. What is the maturity level of the team when it comes to working on the cloud ........ These are just a few of the many questions basis which we do self-assessment or measure our preparedness. Let me know if you need more insights. Happy to help!!