If you don’t need as much RAM, you can take the second option, the Dplsv6 and Dpldsv6 VMs that offer the same number of vCPUs and up to 192GB of RAM. These work well for small workloads, for example, the various components of a microservice architecture.
At the other end of the scale, the third option, are the Epsv6 and Epdsv6 VMs. Here you can configure up to 672GB of RAM, alongside 96 vCPUs. This is suitable for applications that need a lot of in-memory data, allowing you to use Arm hardware for services like Redis. The three different memory models offered by Azure look likely to cover most of the scenarios you’d expect for a modern cloud-native application, allowing you to choose different VMs for different parts of your application.
There’s a wide choice of storage options, with support for all Azure’s remote storage options. If you choose a Dpdsv6, Dpldsv6, or Epdsv6, your VM will come with local NVMe storage (the “d” stands for disk), so you will need a NVMe-ready operating system. Storage amounts vary with the number of vCPUs, starting at 110GB for a 2-vCPU system.