Three to three don't: the basic principle of building a private cloud

There are some successful cases where private cloud computing is used within the enterprise, so the small part thinks that it is time to share with you some of the useful and even harmful points about the private cloud. The number of users who have built a private cloud is not much, but the fundamentals of success are clear. Here's a little set of three points about what to do and what not to do.

"Three wants" of cloud computing

1: Use the SOA properly. While many people view private clouds as simple virtual resources, users who successfully build private clouds generally follow the following path: First, you must start with the needs of the business, then build the architecture, and finally the solution. Without a good architectural foundation, it is difficult to guarantee when your private cloud will succeed and how it will succeed.

2: Consider performance. Using a private cloud can result in low performance, as I've seen many examples. In many cases, applications are not designed for multiple tenants and virtual environments, so many applications must be redesigned to work effectively.

3: Consider security and management. This is no bother, say more than a few times and no harm. Security and management can affect the whole body in terms of architecture.

Cloud computing "three Don't"

1: Do not choose private cloud software based on popular trends. Today's private cloud has two big camps, EMC's VMware Camp and Open Source (Xen, Eucalyptus and others), and according to my focus on these two camps, their members are very determined to use VMware or open source products, and no one is taking the middle road. But to be honest, both solutions have their own advantages both technically and commercially, so be sure to be open-minded when choosing a private cloud environment, try to remain neutral and open, and do more prototyping tests.

2: Do not mistake it for "elastic extensible". You are simply extending the hardware on the rack to a certain extent. Typically, most businesses have only a few servers, so your scalability is very limited. A private cloud is not a public cloud, and you can't use it as a credit card.

3: Don't let the supplier drive you to use any solution. Since there are not many private cloud built for you to refer to, you will probably want to let suppliers include so-called "big software companies" to help you build your own private cloud, from the architecture to the solution. If you do this, don't be surprised if you have problems in the future, because the solutions that vendors pick up for you have sales goals that will make you a tough one in the future. Suppliers have a conflict of interest, so if they are allowed to decide on a solution, they will only pick the ones that meet their own sales needs without considering your business needs.

"Reprint please indicate original author and source"

Original: Building private Clouds:3 dos and 3 don ' TS Author: David Linthicum