Cloud Vendor Specific Database Considerations

Black Duck Alert User Guide

Version
latest

Microsoft Azure

With Microsoft Azure deployments, there are several considerations in terms of storage classes:

  • Azure Disk is node bound. This means that in instances where the database pod terminates, the pod may be scheduled on a different node. This may lead to data loss.

  • Azure File does not support hard links by default and the pod may fail to start. A NFS based azurefile storage class can be created in this instance Microsoft Documentation.

Amazon Web Services

Amazon Elastic Block Store (EBS) is node bound. This means that in instances where the database pod terminates, the pod may be scheduled on a different node. This may lead to data loss.

In general, it is recommended to use an externally managed database in production deployments.