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 If you need a cloud-based service bus or a simple to use queue/topic/routing/pub-sub service, then Azure Service Bus is a very good choice at a reasonable price and performance. Typically on-premise we'd use RabbitMQ because it "just works", but if you're building a "cloud-first" application, then this is the one to go with. It's especially easy to integrate with if you're already embedded in the Microsoft ecosystem.
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 Acting as a basic queuing service it works very well. One of the best parts is that Azure Service Bus can work over HTTPS which helps in strict firewall situations. There is a performance hit if you choose to use HTTPS. The routing capabilities are quite good when using topics and subscriptions. You can apply filters using a pseudo-SQL-like language though the correlation filters are quick and easy options. Costs are very reasonable at low-ish volumes. If you're processing 10's of millions of messages a month... it may be a different story. 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 The SqlFilter could be a little easier to use, but it's not terrible. The performance while using HTTPS for the connection is a little slow compared to direct connections using AMQP ports. There is a size limit to the message - unlike RMQ for instance, Azure Service Bus caps messages to 256kb on the standard tier. 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 RabbitMQ is simple and awesome... but so is Azure Service Bus. Both accomplish the same thing but in different environments. If you're building a cloud-native application - especially one that is serverless by design - Azure Service Bus is the only real choice in Azure. It works well, it's performance, and it's reasonably priced in the Standard tier. From our testing, RMQ is more performant, but it's hard to compare service-based implementations vs RMQ installed on VMs.
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 Compared to open-source free software like RMQ, Azure Service Bus does have some costs to it. But the cost is reasonable. Also unlike RMQ, Azure Service Bus doesn't require you to stand up any hardware - so it's very easy to use and saves time/money from that perspective. Read full review ScreenShots