Loading...
- Layer-2 logical isolation: Builds an isolated network environment based on True IDC Cloud. Layer-2 logical isolation is achieved between different VPC instances.
- Virtual networks are built on a physical network based on the OverLay technology: Network virtualization
- VPC instances are isolated using Vxlan. Layer-2 logical isolation is achieved between different VPC instances to prevent them from communicating: Full isolation among VPC instances
- Custom network environment: You can customize the IP address range, network segment, route table, and gateway. You can also plan and manage the network as needed.
Deploy applications in a safe manner
You can deploy applications in a VPC to provide services to external networks. To control access to the applications over the Internet, you can create security group rules and configure whitelists. You can also isolate application servers from databases to implement access control. For example, you can deploy web servers in a subnet that can access the Internet and deploy databases in another subnet that cannot access the Internet.
Multi-zone disaster recovery
You can create one or more vSwitches to create one or more subnets for the VPC. vSwitches within the same VPC can communicate with each other. To implement cross-zone disaster recovery, you can deploy resources across vSwitches in different zones.
Deploy applications in a safe manner
You can deploy applications in a VPC to provide services to external networks. To control access to the applications over the Internet, you can create security group rules and configure whitelists. You can also isolate application servers from databases to implement access control. For example, you can deploy web servers in a subnet that can access the Internet and deploy databases in another subnet that cannot access the Internet.
Multi-zone disaster recovery
You can create one or more vSwitches to create one or more subnets for the VPC. vSwitches within the same VPC can communicate with each other. To implement cross-zone disaster recovery, you can deploy resources across vSwitches in different zones.
Deploy applications in a safe manner
You can deploy applications in a VPC to provide services to external networks. To control access to the applications over the Internet, you can create security group rules and configure whitelists. You can also isolate application servers from databases to implement access control. For example, you can deploy web servers in a subnet that can access the Internet and deploy databases in another subnet that cannot access the Internet.
Multi-zone disaster recovery
You can create one or more vSwitches to create one or more subnets for the VPC. vSwitches within the same VPC can communicate with each other. To implement cross-zone disaster recovery, you can deploy resources across vSwitches in different zones.
Deploy applications in a safe manner
You can deploy applications in a VPC to provide services to external networks. To control access to the applications over the Internet, you can create security group rules and configure whitelists. You can also isolate application servers from databases to implement access control. For example, you can deploy web servers in a subnet that can access the Internet and deploy databases in another subnet that cannot access the Internet.
Multi-zone disaster recovery
You can create one or more vSwitches to create one or more subnets for the VPC. vSwitches within the same VPC can communicate with each other. To implement cross-zone disaster recovery, you can deploy resources across vSwitches in different zones.
Deploy applications in a safe manner
You can deploy applications in a VPC to provide services to external networks. To control access to the applications over the Internet, you can create security group rules and configure whitelists. You can also isolate application servers from databases to implement access control. For example, you can deploy web servers in a subnet that can access the Internet and deploy databases in another subnet that cannot access the Internet.
Multi-zone disaster recovery
You can create one or more vSwitches to create one or more subnets for the VPC. vSwitches within the same VPC can communicate with each other. To implement cross-zone disaster recovery, you can deploy resources across vSwitches in different zones.
Features:
- Record Types: Supports the following types of DNS records: A, AAAA, CAA, MX, CNAME, TXT, NAPTR, PTR, NS, and SRV.
- DNS Query Attacks: Supports real-time attack detection and abnormal traffic handling and processes up to hundreds of millions of DNS queries per second.
- Real-time Monitoring and Alerting: Performs 24/7 monitoring to promptly identify exceptions and send alerts to O&M personnel.
- IPv6 Support: Supports IPv6-based AAAA records and provides DNS servers that support access from IPv6 addresses.
Build a website
With an A record, you can associate a website domain name with the IP address of the Web server to ensure that the website is accessible.
Send and receive emails
With an MX record, you can configure DNS records based on the configurations provided by the mailbox provider to ensure that you can send and receive emails.
Balance load across servers
If multiple servers serve the same business, you can use the weighted round-robin mechanism to balance loads across servers.
Build a website
With an A record, you can associate a website domain name with the IP address of the Web server to ensure that the website is accessible.
Send and receive emails
With an MX record, you can configure DNS records based on the configurations provided by the mailbox provider to ensure that you can send and receive emails.
Balance load across servers
If multiple servers serve the same business, you can use the weighted round-robin mechanism to balance loads across servers.
Build a website
With an A record, you can associate a website domain name with the IP address of the Web server to ensure that the website is accessible.
Send and receive emails
With an MX record, you can configure DNS records based on the configurations provided by the mailbox provider to ensure that you can send and receive emails.
Balance load across servers
If multiple servers serve the same business, you can use the weighted round-robin mechanism to balance loads across servers.
Build a website
With an A record, you can associate a website domain name with the IP address of the Web server to ensure that the website is accessible.
Send and receive emails
With an MX record, you can configure DNS records based on the configurations provided by the mailbox provider to ensure that you can send and receive emails.
Balance load across servers
If multiple servers serve the same business, you can use the weighted round-robin mechanism to balance loads across servers.
Build a website
With an A record, you can associate a website domain name with the IP address of the Web server to ensure that the website is accessible.
Send and receive emails
With an MX record, you can configure DNS records based on the configurations provided by the mailbox provider to ensure that you can send and receive emails.
Balance load across servers
If multiple servers serve the same business, you can use the weighted round-robin mechanism to balance loads across servers.
- Monitor EIPs: EIP is integrated with a cloud monitor or a management tool to help you collect a variety of monitoring metrics and generate time series graphs in the EIP console. You can troubleshoot issues based on the metrics.
- Fine-grained monitoring: You can use this feature to monitor Internet traffic in real time and adjust the EIP bandwidth promptly.
- Manage idle EIPs: This feature can display idle EIPs in the EIP console. You can manage idle EIPs to reduce costs.
- View operation records: You can use this feature to view the operation records of EIP, which facilitates troubleshooting and issue locating.
Migrate Workloads from Data Centers to True IDC Cloud
Problem
The current network connections have high network latency and poor scalability, and cannot meet market requirements.
Solution
Elastic IP Address allows you to migrate public IP addresses to True IDC Cloud without changes. This reduces migration costs and losses.
Migrate Workloads from Data Centers to True IDC Cloud
Problem
The current network connections have high network latency and poor scalability, and cannot meet market requirements.
Solution
Elastic IP Address allows you to migrate public IP addresses to True IDC Cloud without changes. This reduces migration costs and losses.
Migrate Workloads from Data Centers to True IDC Cloud
Problem
The current network connections have high network latency and poor scalability, and cannot meet market requirements.
Solution
Elastic IP Address allows you to migrate public IP addresses to True IDC Cloud without changes. This reduces migration costs and losses.
Migrate Workloads from Data Centers to True IDC Cloud
Problem
The current network connections have high network latency and poor scalability, and cannot meet market requirements.
Solution
Elastic IP Address allows you to migrate public IP addresses to True IDC Cloud without changes. This reduces migration costs and losses.
Migrate Workloads from Data Centers to True IDC Cloud
Problem
The current network connections have high network latency and poor scalability, and cannot meet market requirements.
Solution
Elastic IP Address allows you to migrate public IP addresses to True IDC Cloud without changes. This reduces migration costs and losses.
True IDC Cloud offers Server Load Balancer (SLB) instances, including the following types:
Classic Load Balancer (CLB): CLB supports TCP, UDP, HTTP, and HTTPS protocols. It provides advanced Layer 4 processing capabilities and basic Layer 7 processing capabilities.
Performance:
- Developed on a reliable physical machine architecture.
- Capable of handling up to 200,000 connections, ensuring optimal performance.
Distribute workloads
CLB instances route traffic to Elastic Compute Service (ECS) instances that act as backend servers based on listening rules. This allows you to avoid overloaded servers that may negatively affect user experience. The session persistence feature can be used to forward all requests from a client to the same backend ECS instance to improve access efficiency.
Eliminate single points of failure (SPOFs)
CLB instances act as the single point of contact for clients. You can add multiple ECS instances to a CLB instance. When an ECS instance malfunctions, CLB automatically isolates the ECS instance and distributes inbound requests to other healthy ECS instances. This ensures that your applications continue to run as expected.
Distribute workloads
CLB instances route traffic to Elastic Compute Service (ECS) instances that act as backend servers based on listening rules. This allows you to avoid overloaded servers that may negatively affect user experience. The session persistence feature can be used to forward all requests from a client to the same backend ECS instance to improve access efficiency.
Eliminate single points of failure (SPOFs)
CLB instances act as the single point of contact for clients. You can add multiple ECS instances to a CLB instance. When an ECS instance malfunctions, CLB automatically isolates the ECS instance and distributes inbound requests to other healthy ECS instances. This ensures that your applications continue to run as expected.
Distribute workloads
CLB instances route traffic to Elastic Compute Service (ECS) instances that act as backend servers based on listening rules. This allows you to avoid overloaded servers that may negatively affect user experience. The session persistence feature can be used to forward all requests from a client to the same backend ECS instance to improve access efficiency.
Eliminate single points of failure (SPOFs)
CLB instances act as the single point of contact for clients. You can add multiple ECS instances to a CLB instance. When an ECS instance malfunctions, CLB automatically isolates the ECS instance and distributes inbound requests to other healthy ECS instances. This ensures that your applications continue to run as expected.
Distribute workloads
CLB instances route traffic to Elastic Compute Service (ECS) instances that act as backend servers based on listening rules. This allows you to avoid overloaded servers that may negatively affect user experience. The session persistence feature can be used to forward all requests from a client to the same backend ECS instance to improve access efficiency.
Eliminate single points of failure (SPOFs)
CLB instances act as the single point of contact for clients. You can add multiple ECS instances to a CLB instance. When an ECS instance malfunctions, CLB automatically isolates the ECS instance and distributes inbound requests to other healthy ECS instances. This ensures that your applications continue to run as expected.
Distribute workloads
CLB instances route traffic to Elastic Compute Service (ECS) instances that act as backend servers based on listening rules. This allows you to avoid overloaded servers that may negatively affect user experience. The session persistence feature can be used to forward all requests from a client to the same backend ECS instance to improve access efficiency.
Eliminate single points of failure (SPOFs)
CLB instances act as the single point of contact for clients. You can add multiple ECS instances to a CLB instance. When an ECS instance malfunctions, CLB automatically isolates the ECS instance and distributes inbound requests to other healthy ECS instances. This ensures that your applications continue to run as expected.