Azure Blob 存储与 Azure 驱动器
我正在考虑迁移到 Windows Azure 而不是典型的托管，但我不确定如何最好地存储图像。经过搜索，我发现有 2 种可能的解决方案 - Blob 存储或 Azure 驱动器。
我研究过 Blob 存储，尽管我已经开始习惯这个想法，但它需要对我们的 CMS 进行大量修改。在我的搜索中，我刚刚偶然发现了 Azure Drive，如果我理解正确的话，它会创建一个虚拟硬盘驱动器，允许您的应用程序像在普通服务器上一样运行。
与 Blob 存储相比，Azure Drive 是否有任何缺点？听起来使用 Azure Drive 而不是 Blob 存储将当前应用程序迁移到 Azure 会容易得多，但我只是想检查一下这是否存在任何重大缺陷。
谢谢帕特
I am looking at moving to Windows Azure rather than typical hosting however I'm unsure how best to store images. After searching I've found that there are 2 possible solutions - Blob storage or Azure drive.
I have looked into Blob storage and although I have begun to get used to the idea it will require quite a lot of modification to our CMS. In my searching I have just stumbled across Azure Drive which if I understand correctly creates a virtual hard drive which allows your application to run as it would on a normal server.
Are there any disadvantages to Azure Drive over blob storage? It sounds like migrating current applications to Azure will be much easier with Azure Drive rather than Blob storage but I just wanted to check that there weren't any major flaws in this.
Thanks
Pat
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
是的，有很多差异。首先，Windows Azure 驱动器实际上是作为页 blob 上传的 VHD，并由驱动程序安装以提供 NTFS 分区。因此，要获取其上的任何数据，您必须安装它（或快照）。如果不安装，则无法直接访问数据。
接下来，只能通过一个实例为 RW 安装驱动器。如果您想要其他任何内容来读取该驱动器，则必须创建快照并挂载，这会引入“过时”问题，导致仅读取正在挂载快照的实例。您可以使用 SMB 共享来解决此问题，但这稍微复杂一些。
如果您也使用驱动器，您将无法自动获取 CDN 功能。
驱动器非常适合其预期用途 - 让必须使用 NTFS 的应用程序在 Windows Azure 中运行。
如果您要在本机使用 Blob，您将 a.) 让存储子系统进行扩展并从实例中移除用于提供数据的负载，b.) 能够使用 CDN 来获取地理规模
图像也是如此。
虽然这需要一些工作，但我强烈建议将图像放入 blob 存储中。它非常适合它。
Yes, there are quite a few differences. First, the Windows Azure drive is actually a VHD uploaded as a page blob and mounted by a driver to provide a NTFS partition. So, to get any data on it, you must mount it (or a snapshot). Data is not directly accessible without mounting.
Next, Drives can only be mounted for RW by one instance. If you want anything else to even read that drive, you must snapshot and mount, which introduces a 'staleness' problem to read only instances that are mounting snapshots. You can work around this with an SMB share, but that is slightly complicated.
You would lose the ability to automatically get CDN capabilities if you used a drive as well.
Drives are great for their intended purpose - getting applications that must use NTFS to work in Windows Azure.
If you were to use Blobs natively, you would a.) get the storage subsystem to scale and remove the load from your instances for serving the data and b.) be able to use the CDN to get geoscale on the
images as well.
While it is some work, I would strongly recommend putting images in blob storage. It is ideal for it.