THE INFORMATION IN THIS ARTICLE APPLIES TO:

• EFT, all versions

QUESTION

Can I use Azure Blob Storage in an EFT HA cluster?

ANSWER

Azure Blob Storage is not a supported platform for the shared configuration path in an EFT HA cluster. (Blob can used for user data as either the Site root or a virtual folder in VFS.)

• Pros:
• Designed for shared access across multiple VMs, which is ideal for EFT HA cluster nodes.
• Offers low latency for frequent file access, important for configuration updates.
• Supports file locking mechanisms to avoid data corruption during simultaneous access by cluster nodes.
• Cons:
• Might be more expensive compared to blob storage for storing just configuration files.

• Pros:
• Generally cheaper than file shares for storing static data like configurations.
• Highly scalable for large configurations.
• Cons:
• Not designed for shared access like file shares. Requires additional configuration for EFT to access the blob storage as a shared resource.
• Might have higher latency compared to file shares.
• Lacks built-in file locking mechanisms, increasing complexity for managing concurrent access.

In summary:

• Use Azure file shares for simplicity and ease of configuration in your EFT HA cluster, especially if performance and data integrity are critical.
• Consider Azure blob storage if cost is a major concern and your configuration files are relatively static. However, be prepared for additional setup and potential performance trade-offs.