Microsoft's Blob Storage system on Azure is designed to make unstructured data available to customers anywhere through REST-based object storage.
$0.01
per GB/per month
Azure Data Factory
Score 9.0 out of 10
N/A
Microsoft's Azure Data Factory is a service built for all data integration needs and skill levels. It is designed to allow the user to easily construct ETL and ELT processes code-free within the intuitive visual environment, or write one's own code. Visually integrate data sources using more than 80 natively built and maintenance-free connectors at no added cost. Focus on data—the serverless integration service does the rest.
N/A
Pricing
Azure Blob Storage
Azure Data Factory
Editions & Modules
Block Blobs
$0.0081
per GB/per month
Azure Data Lake Storage
$0.0081
per GB/per month
Files
$0.058
per GB/per month
Managed Discs
$1.54
per month
No answers on this topic
Offerings
Pricing Offerings
Azure Blob Storage
Azure Data Factory
Free Trial
Yes
No
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
Azure Blob Storage
Azure Data Factory
Considered Both Products
Azure Blob Storage
Verified User
Anonymous
Chose Azure Blob Storage
Blob storage lets us control the file source/hosting and retain everything within our Microsoft ecosystem. Blob is less feature-rich than some of the other products. Still, we consider it as a value-added product included within our environment, and alternative products are not …
Azure Blob Storage was used only because we were already using it for other projects, and it has a good reputation for being a reliable cloud provider. It also has widespread regional availability and allows for data replication. It can also be easily accessed via the API or by …
We didn't actually evaluate anything but Azure Blob Storage since it worked so well for backups and Audit logs and the price point was good enough for us.
Azure Blob Storage is the best choice to store files when the app runs in Azure. It also has some advantages over S3, like Shared Access Signatures, that make it easy to control access to files directly via a URL. Azure Blob Storage is very fast and we have not had any major …
S3 seemed to be just as functional as blob storage in our analysis. The only real difference is we already were on the Microsoft platform with 365, and it was an easy system to continue to learn. That was the only real deciding factor between the two that made any difference …
Ease of use and availability to actual usage makes it my first choice. I feel like IBM Cloud is where azure was 5 years ago in terms of implementation and ease of use. AWS has some great functionality but it almost feels like you need to learn how to work under the hood of a …
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 …
Azure Data Factory helps us automate to schedule jobs as per customer demands to make ETL triggers when the need arises. Anyone can define the workflow with the Azure Data Factory UI designer tool and easily test the systems. It helped us automate the same workflow with …
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.
I'd chose data factory because its very easy to use, its UI is beautiful, it's library for .net is very useful and it lives within the microsoft ecosystem.
Azure Data Factory is a relatively new player in the space, and its feature set marks it as such. It does not have the full features of a more mature product set such as any of the above. However, it does allow for the creation of ETL/ELT flows/pipelines with minimal initial …
Azure Blob Storage is well suited for cases where you are working with different data formats and looking for cost-effective storage solutions based on access frequency. Another area of strength is the encryption of data at rest, and encryption can be managed on your own. However, it may not be appropriate for transferring large data very fast.
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.
Reduced cost. We were able to reduce our storage infrastructure by several hundred terabytes by consolidating redundant copies and dedupe/compression on files.
Extremely high level of redundancy. We can replicate data in a variety of ways that we would never have been capable of on our own hardware.
If we are transferring huge amount of data (outbound), it can get quite expensive.
With new features being added constantly, although a good thing, at times it becomes difficult to keep up with the changes. Documentation needs to keep UpToDate and should include best practices.
Performance can be improved especially when it comes to cold storage.
Blob storage is fairly simple, with several different options/settings that can be configured. The file explorer has enhanced its usability. Some areas could be improved, such as providing more details or stats on how many times a file has been accessed. It is an obvious choice if you're already using Azure/Entra.
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.
Documentation sometimes appears to be out of date or not fully documented properly with new releases. It is like documentation comes out for a specific version and is quickly out of date. Another issue is documentation is scarce on new releases and only seems to get properly updated (and sometimes is still wrong) once enough people hit the forums to complain.
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
Blob storage lets us control the file source/hosting and retain everything within our Microsoft ecosystem. Blob is less feature-rich than some of the other products. Still, we consider it as a value-added product included within our environment, and alternative products are not needed for our requirements. Keeping the hosting within our tenant locale is vital to us.
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.