What is our primary use case?
Data Lake Storage is primarily used to ingest different types of data such as file share data, raw data, or unstructured data.
Additionally, the Data Lake Storage account is Gen Two and is integrated with various Azure resources such as Azure Cloud, Databricks, Data Factory, and SQL DB. Furthermore, it is also compatible with other solutions such as Cosmos DB, Stream Analytics, and Event Hubs.
What is most valuable?
Data Lake Storage provides valuable features such as access keys, container strings, lifecycle management, audit logs, and the soft delete option. These features help in cost-saving and provide an excellent mechanism for backing up data.
Furthermore, Data Lake Storage can interact with any other Azure resources, providing seamless integration and connectivity.
What needs improvement?
Improvement is needed in the migration process from Lakehouse to Enterprise Data Lake (EDL). Currently, migration is only one-way possible, and it would be beneficial if this aspect could be improved. Additionally, increasing the retention period beyond the current seven days would be helpful.
For how long have I used the solution?
I have been working with Data Lake Storage for around five years.
What do I think about the stability of the solution?
Stability is rated around eight to nine out of ten. It has very good reliability and dependability.
What do I think about the scalability of the solution?
For scalability, I rate Data Lake Storage around eight to nine on a scale of one to ten.
How are customer service and support?
The technical support from Microsoft is pretty good. The support team is very supportive, and most issues are resolved quickly once we get in touch with them.
How would you rate customer service and support?
How was the initial setup?
The initial setup process is simple. There are different deployment methods, including deploying manually via the portal or using Terraform modules.
What's my experience with pricing, setup cost, and licensing?
The pricing for Data Lake Storage depends on several factors, like the configuration for multiple or single locations and if it uses geo-redundancy storage, which is beneficial but consumes higher costs. Enabling lifecycle management and using cost-saving features can keep the expenses in check.
Which other solutions did I evaluate?
There are several competitors to Data Lake Storage, such as AWS, Google Cloud Storage, IBM Object Storage, and Snowflake.
What other advice do I have?
It is essential to enable lifecycle management in Data Lake Storage for better cost management. Proper setup according to your use case and employing strategies like using cold or archive tiers can save cost and optimize usage.
I'd rate the solution nine out of ten.