The reason to choose vsphere

In the process of migrating to a public cloud, small and medium-sized enterprises face many choices, and in the first series of these two-part series, the salient advantages of some public clouds, including saving management time, increasing data center scalability, and eliminating security and usability concerns, have been addressed. Some other enterprises, however, should continue to use the vsphere infrastructure that is managed internally, and the following factors may make it easier for you to decide to choose vsphere.

Paranoid Security Team

No company likes to hear that their data is in an insecure environment, and some companies are not even likely to take the risk. In this case, IT infrastructure needs to remain in the data center, managed by the internal IT team. This requires the use of internal resources under strict security measures, but it also implies the need to be familiar with environmental security and the right to full control. Companies associated with government management must consider security issues, which will prevent them from migrating to private clouds.

Resource and quota control

Very few private cloud providers give the same level of access to a single user VMware virtualization environment to adjust resource allocations in the environment with maximum programs. Private vsphere environments can also avoid mutual interference, and a virtual machine in the resource stack consumes more system resources than it needs, inadvertently creating a resource shortage with other virtual machines in the system. Network traffic flooding such a simple event or management system in the CPU management of the use of such complex tasks, will cause this phenomenon.

Support for bandwidth-sensitive applications

Removing server-side applications from end users, or deploying servers separately in one integrated implementation, needs to be sure that network bandwidth between two sites meets the traffic needs of all applications. Deploying the application server and the three-tier database servers in two different sites may not be a wise decision, as there is a need to exchange large amounts of network traffic between them. If the end-user's application requires a large network traffic exchange with the backend server, the server should be deployed to the same location as the desktop-unless it is a virtual desktop and able to migrate to the cloud.

The concerns of IT department and the origin of personal factors

In addition to technical factors, there are some concerns and personal factors that affect important decisions. Migrating to the public cloud, coordinating these factors is as important as planning network bandwidth. For example, internal IT staff may worry about losing their current job or reducing their job responsibilities, and other negative ideas include a public cloud that increases security risks.

Reasonable planning overhead

Overhead is a critical factor in discussions about migrating to a public cloud or maintaining a local vsphere VMware virtualization environment. From the point of view of capital investment, the simple implementation of internal virtualization cost is smaller than migrating to public cloud. When infrastructure is deployed within the company, SMEs can design and implement various components to meet their specific needs and private applications. The inherent redundancy in the public cloud also does not apply to all applications, and increases overhead during system implementation.

Recommendations

If you still can't decide whether to migrate to a private cloud or run an internal vsphere infrastructure, see how you can meet your IT needs based on the four tips below:

1. Understand the public cloud platform. How does the cloud service provider ensure environmental security, both from external threats and from the isolation of different users? How to prevent interference from other users?

2. For extremely sensitive data, consider using a hybrid cloud model. Non-critical data can easily be migrated to a shared cloud platform, but core data should still be kept on the internal management platform.

3. Negotiate an achievable service level agreement (SLA) with the public cloud service provider. The loss of service termination and data loss is different for every company, and each SME needs to negotiate its own service level agreements.

4. If there is doubt about putting all production environments in the public cloud, small and medium-sized enterprises can first move some non-critical resources to test them, such as disaster recovery. Once you have adapted to this scenario, migrate the disaster recovery data back to the internal data center and move the production environment to the public cloud.

(Responsible editor: The good of the Legacy)