You might have seen many articles on private cloud or a public cloud, but a cloud strategy is not limited to this only. The answer may be in an intermediate range, the Hybrid Cloud.
First of all, let’s see how these services are deployed.
Private cloud – internalized or externalized: A private cloud is a cloud infrastructure operated directly and exclusively by an organization. The best known example is that of a cloud that runs on an internal IT company. Obviously, this infrastructure can be internalized. Under these conditions it is operated by the IT teams. Or it can be outsourced to a hosting company, specialized in cloud services.
In both cases, the infrastructure can be physically being in the company (on-premise), or outside the premise, and then we say that it is hosed. But in both cases, only the organization operates and supports the load.
A private cloud is primarily a natural movement of the company. The infrastructure that has funded by deployed, maintained, energized, powered, and updated applications on the regular basis usually provide the first support for cloud projects consumed by the enterprise and its ecosystem.
Services deployed in the cloud are therefore based on an infrastructure in internal control. And it is reassuring for CIOs shows the use of equipment purchased in time. It can better justify spending equipment and keep their hands on the edge of the information system and all that is within the boundary.
In many companies, business applications cannot be conceived outside of the physical infrastructure of the company. In some cases, this is a safety issue. For example, Bank data, health Care, Defense, etc. In other cases, it is a question of attitude.
In all cases, the private cloud is an economical choice. The information from here in the case of system investments and the company fully supports funding.
A public cloud is based on open and shared public infrastructure. All users connect to the same infrastructure to access the same services that are rented. All users coexist within this infrastructure: developers to ensure data isolation of each other.
If there are several levels of membership to a public cloud, we consider two:
Public infrastructure: the company occupies and rent a place in the infrastructure of the hosting company for the service in the cloud. It makes available virtualized resources – servers with their operating systems, storage with databases, and network to communicate – it consumes resources according to the needs. These resources are virtualized, that is to say are running in virtual machines (VM). Hundreds of virtual machines running on a physical machine, so many companies or individuals may be present on the same machine, called open architecture. The advantage for the company is that by sharing the same infrastructure with other companies cut the cost. And management, such as maintenance of the infrastructure is provided by the hosting company.
The multitenant: users participate and praise the same service, whatever the resources, infrastructure, management of servers, and storage, which is an application that is available with the storage of data. The user pays for a service, often with a clause volume changed the price down as well as up depending on the number of users and the use of storage space or data exchanged and processed. The service will be displayed on the workstation, usually in a browser internet. Some of these services ‘public cloud’ is already used by many organizations, such as messaging offered by the search engines or e-commerce websites, or CRM solutions – managing the customer relationship, even some payroll system programs.
The advantage for the company is to first be able to have multiple services without having to invest in infrastructure and licenses, and rapidly deployable since it is adequate to connect and declare it to start operations.
Another advantage is that you can always use the latest version of the solution, without the need to provide updates. Deployment is flexible and related to the only operating expenses. Finally, the solution to the public cloud is also interesting; mobility users can have the same tools as they connect.
hybrid cloud: the principle of flexibility
We have almost seen every version of cloud displays its advantages and disadvantages. The choice of one or the other is often dictated by necessity or by company policy. For example, the private cloud can keep the control of its information system, while the public cloud offers greater flexibility in the deployment of shared services.
When a company enforces a strict and restrictive discipline, it focuses on the infrastructure it owns, obviously oversized to be able to withstand peak loads, but under its full control. Conversely, it can select more flexibility, but lose that sense of security by using the cloud, sometimes at the risk of getting lost. Cloudiness prevailing on certain clauses of reversibility demonstrated.
However, there is an intermediate position which may enable the company to benefit from the best of both worlds: the hybrid cloud. This is a composition of two clouds, and the company can take advantage of two deployment models of cloud services.
The hybrid cloud considered for its flexibility. Some examples: components and strategic and highly secure applications of information systems can be deployed internally in a private cloud, components and operation applications, accessories, services and architectures for development and testing can appeal to public cloud services.
These may also cover temporary needs or meet the objectives of proximity access, for example, based on hosting company that has a network of data centers in the world, which can improve the availability of service and reduce latency.
Building hybrid cloud architecture can go further with what we call the ‘cloud bursting’. The system displays information using two levels; the average level is the most common since it covers 80 to 90% (or more) of the consumption of material resources, and come to peak loads, in those rare moments the year when excess needs (e.g. Balances and year-end holidays in the trade) cause additional load to which the SI (Sustainable Infrastructure) must meet.
The architecture ‘on premise’ must accept these peaks, so all SI is oversized compared to the real needs of the company means. The ‘cloud bursting’ is to see the peaks of consumption of infrastructure resources in the cloud. ISD (Infrastructure Services Division) can resize and its information as accurately as not invest in ‘capex’ (Capital expenditures) – and private cloud. Its permanent needs a replay in ‘opex’ (operating expense) needs at the margin.
That is why the hybrid cloud architectures should quickly establish itself to companies who are in search of the security of an internalized SI and flexibility of an IaaS in the cloud. The process is even more important that we go through a period of technological revolution, both the evolution of equipment and tools, especially the Virtualization infrastructure, and changes in use, especially consumerization in IT and mobility.
By Paul Lopez,
Paul a technology writer and sales & marketing executive at bodHOST.com, a cloud & dedicated server hosting company based in New Jersey.
