Build cloud storage to compare the difference between private cloud and public cloud

The metaphor of cloud storage may be a bit exaggerated, but we can still feel the vague concepts associated with the cloud, and the future of this technology is full of unknowns, as is the case with private cloud storage as we know it. While private cloud stores on the market claim to benefit from the addition of firewalls to the existing public cloud, there are indications that private cloud storage has fallen to public storage.

Speaking of public storage, it is difficult not to associate with the selective outsourcing of the post-network company era, but nonetheless, it is simple and inherently available. The name of the public store does not sound proprietary, much like putting things directly in there without being managed in an orderly fashion. And to be honest, the word "public" doesn't sound as cool as "cloud".

What is the difference between a private cloud and a public cloud?

The name change does not change its nature, it is still a storage architecture technology that provides a better service. What we have to admit is that regardless of which brand of product is selected, the enterprise will benefit from the private cloud architecture chosen. In a sense, the emergence of the private cloud market is the result of the development of the public cloud. One we have to admit is that storage is an irreplaceable part of a cloud solution, whether it's a public cloud or a private cloud. In particular, for server virtualization, cloud computing can be applied. Nevertheless, a mature storage strategy is essential to ensure a successful deployment of the cloud.

Compared to the advantages of public cloud storage, we find that private cloud storage has some of the following features:

• availability. When the user needs, space needs can be distributed in a timely manner, and require the timely recovery after use.

• Quality of service. Detailed service level descriptions are required and strictly referenced. Measurable metrics can be used to define how well the response time, recovery time, and activity time are supported by the user.

• Cost fixing. In a cloud environment, the charge is usually based on storage per unit. The user simply pays for the portion of the actual use based on the service level agreement, rather than on the allocated space or a certain standard.

When you look at the cloud storage price list, you tend to see some tempting concessions, but who really benefits from it? There is a clear distinction between public and private clouds. In the public cloud architecture, users and organizations that sign agreements will benefit. For the user, they will have all the support of the application, for the organization, the cost is relatively fixed, perhaps compared to the maintenance of a system is cheaper. The IT department needs to tell the cloud service provider that the platform is the precise definition of the service. Although the cost of the business unit is relatively fixed, the public cloud also has a "how much to buy" refund advantage, and there are specific service level agreements, and unfortunately, these standards do not adapt to the IT department. Users need to get enough storage space and start to manage it, monitor the system and start detailed costing.

Also, it should be noted that these benefits do not mention "using the most advanced storage arrays", "Fastest disk" or "10Gb Ethernet." In fact, there are no relevant technical guidelines. The public cloud focuses on better operations: service levels, cost control, and fast response capabilities. Storage vendors, however, tend not to focus on operational issues, they are simply selling hardware and software. So what do these vendors sell for the private cloud? To be sure, it's definitely not just a hardware upgrade and a fantasy. Fortunately, this has been confirmed. As long as the private cloud can be applied to the correct environment and configuration, it will never be just a hardware concept.

When it comes to cloud architecture, some vendors emphasize scalability and flexibility requirements. It is certain that the relatively low cost cloud architecture model will be more attractive. But almost every vendor will claim that they have such attributes, so these definitions are less useful. In addition, cloud deployment refers not only to the hardware architecture, as the cloud develops to the end and the process is more meaningful than the product itself.