The instance type family determines the hardware configuration and computing power of the Virtual Machines. JD Cloud provides four types of instances: general, compute optimized, memory optimized, and high frequency compute. The instance type family and instance type can be selected according to different scenarios and business volume. It supports to adjust instance type at any time to respond to business changes. Single instance can choose 72vCPU and 576GB of memory to the most.
Image is the service running environment, you can choose it by yourself. JD Cloud provides public image, private image and cloud marketplace image. The public image includes multiple released versions of CentOS, Ubuntu, and Windows Server. The private image is the image that you created for the Virtual Machines that have completed environment deployment. The cloud marketplace image is produced, operated and maintained by the service provider (including JD Cloud service team), which integrates the running environment or software and can realize a complete backup of the operating environment and data so as to further enable service recovery or rapid deployment in batches. You can also share the private image with other JD Cloud accounts.
Cloud Disk Service is Block Storage Service provided by JD Cloud for Virtual Machines. Data in Cloud Disk Service are stored in multiple real-time copies. Cloud Disk Service can expand data bucket quickly in a few minutes to achieve persistent storage of data. It provides 5 storage options including performance-oriented SSD Cloud Disk, general SSD Cloud Disk, capacity-oriented HDD Cloud Disk, SSD Cloud Disk and Premium HDD Cloud Disk. It supports incremental snapshots, and the snapshot can be used for creating Cloud Disk Service or restoring the original disk data to snapshot time point.
Virtual Private Cloud (VPC) is the network environment for your customized logical isolation. It supports self-planning network deployment, including preset/non-preset network range (CIDR), subnet segment, routing policy, etc., and can realize multi-level security protection through security groups and network ACLs. Meanwhile, the existing networks can be extended through VPC peering connection or direct connect service. The elastic IP is a public address that can be applied for independently, which supports dynamic associating and disassociating. The network bandwidth can be dynamically adjusted without shutting down. When an instance fails, the elastic IP can drift to the redundant instance to achieve fast response to the fault.
The instance template is the configuration information template for creating a VM instance provided by JD Cloud, including the image, instance type, type and capacity of system disk & data disk, VPC and subnet configuration, security group, and login information, etc. Creating instance by instance template does not need to re-specify the parameters that are included in the instance template. You can create the Virtual Machines of the same instance type for multiple times so that the service deployment time can be shortened.
The Availability Group is a physical distributed disaster-tolerant deployment solution provided by JD Cloud across the availability zones. The Virtual Machines in the group are deployed in multiple fault domains in the data center to minimize the impact of local faults on the overall availability application. The Availability Group can enable the Automatic Scaling feature to automatically expand and shrink capacity along with application load fluctuations.
It provides OpenAPI and console to manage the Virtual Machines, such as creating, starting and stopping. At the same time, you can login the Virtual Machines for environment configuration by using the console VNC and remote SSH.
The Virtual Machines supports two billing methods, i.e., billing by monthly package and billing by configuration. The former method shall be prepaid, with one-time payment covering 1-9 months or 1-3 years, which is applicable for scenarios where the business demand can be estimated in advance (applicable to scenarios where the number and size of instances can be estimated in advance), and the price is more favorable than the latter method.
Pay by configuration is a pay-as-you-go method, which provides more flexible lifecycle management. The billing period is 1 hour and is settled according to the purchased VM instance type and service duration (accurate to second). Switching from billing by configuration to monthly package is supported.
It is recommended to select pay by configuration in the initial test phase and select the appropriate instance type according to the test results, and then switch to the monthly package to save costs.