Likelihood to Recommend Well-suited Scenarios for Azure Data Factory (ADF): When an organization has data sources spread across on-premises databases and cloud storage solutions, I think Azure Data Factory is excellent for integrating these sources. Azure Data Factory's integration with Azure Databricks allows it to handle large-scale data transformations effectively, leveraging the power of distributed processing. For regular ETL or ELT processes that need to run at specific intervals (daily, weekly, etc.), I think Azure Data Factory's scheduling capabilities are very handy. Less Appropriate Scenarios for Azure Data Factory: Real-time Data Streaming - Azure Data Factory is primarily batch-oriented. Simple Data Copy Tasks - For straightforward data copy tasks without the need for transformation or complex workflows, in my opinion, using Azure Data Factory might be overkill; simpler tools or scripts could suffice. Advanced Data Science Workflows: While Azure Data Factory can handle data prep and transformation, in my experience, it's not designed for in-depth data science tasks. I think for advanced analytics, machine learning, or statistical modeling, integration with specialized tools would be necessary.
Read full review They're great to embed logic and code in a medium-small, cloud-native application, but they can become quite limiting for complex, enterprise applications.
Read full review Pros It allows copying data from various types of data sources like on-premise files, Azure Database, Excel, JSON, Azure Synapse, API, etc. to the desired destination. We can use linked service in multiple pipeline/data load. It also allows the running of SSIS & SSMS packages which makes it an easy-to-use ETL & ELT tool. Rajarshi Maitra Director/Client Engagement Leader- P&C Insurance (Digital Transformation)
Read full review They natively integrate with many triggers from other Azure services, like Blob Storage or Event Grid, which is super handy when creating cloud-native applications on Azure (data wrangling pipelines, business process automation, data ingestion for IoT, ...) They natively support many common languages and frameworks, which makes them easily approachable by teams with a diverse background They are cheap solutions for low-usage or "seasonal" applications that exhibits a recurring usage/non-usage pattern (batch processing, montly reports, ...) Read full review Cons Limited source/sink (target) connectors depending on which area of Azure Data Factory you are using. Does not yet have parity with SSIS as far as the transforms available. Read full review My biggest complaint is that they promote a development model that tightly couples the infrastructure with the app logic. This can be fine in many scenarios, but it can take some time to build the right abstractions if you want to decouple you application from this deployment model. This is true at least using .NET functions. In some points, they "leak" their abstraction and - from what I understood - they're actually based on the App Service/Web App "WebJob SDK" infrastructure. This makes sense, since they also share some legacy behavior from their ancestor. For larger projects, their mixing of logic, code and infrastructure can become difficult to manage. In these situations, good App Services or brand new Container Apps could be a better fit. Read full review Support Rating 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
Read full review Alternatives Considered The easy integration with other Microsoft software as well as high processing speed, very flexible cost, and high level of security of
Microsoft Azure products and services stack up against other similar products.
Read full review This is the most straightforward and easy-to-implement server less solution. App Service is great, but it's designed for websites, and it cannot scale automatically as easily as Azure Functions. Container Apps is a robust and scalable choice, but they need much more planning, development and general work to implement. Container Instances are the same as Container Apps, but they are extremely more limited in termos of capacity.
Kubernetes Service si the classic pod container on Azure, but it requires highly skilled professional, and there are not many scenario where it should be used, especially in smaller teams.
Read full review Return on Investment It is very useful and make things easier Debugging can improve Its better suited than other products with the same objective Read full review They allowed me to create solutions with low TCO for the customer, which loves the result and the low price, that helped me create solutions for more clients in less time. You can save up to 100% of your compute bill, if you stay under a certain tenant conditions. Read full review ScreenShots