Among the core features of our ADLS Generation 2 are Hadoop compatible access: so Data Lake Storage Generation 2 allows you to manage and access data just as you would with the Hadoop distributed file system. Because these capabilities are built on Blob Storage, you also get low‑cost, tiered storage with high availability and disaster recovery capabilities. For example, Data Lake Storage Generation 2 provides file system semantics, file‑level security, and the scale.
Data Lake Storage Generation 2 converges the capabilities of Azure Data Lake Storage Generation 1 with Azure Blob Storage. So the Azure team built a new Data Lake service over Blob Storage, Azure Data Lake Storage Generation 2. Azure Data Lake Generation 1, but it lacked the scalability, security, high availability, and overall any good feature Blob Storage has. Within Azure, another service offered this filtering capability and hierarchical namespaces to the work we want. Containers only provide some virtual file system interface for human readability. This means that any time you need a file from Blob Storage, you need to fetch it specifically by URL or get all the elements from that blob. Everything is flat and there is no query syntax. Blob Storage is amazing because it is the cheapest and fastest way to store data, but there is a price. It may seem that this means that a container physically isolates the images from the video in the Blob Storage account, right? However, this is not true. Blob Storage offers three types of resources, the storage account, a container in the storage account, and a blob in a container. Azure Blob Storage is at the core of most Azure services, as well as most organizations in the world.
0 kommentar(er)
