Skip to main content

Definition of Private Cloud


In the last month a lot of people started to talk about private cloud. When people refer to private cloud, they already have an image in their mind with machines that are hosted by them.
The “private cloud” term in general don’t refer to a cloud (like Windows Azure) that is hosted by the client.
The term “private cloud”, that now is used more and more refers to a computing power and storage that is accessible by only a limited numbers of devices (machines). This private network that is created can be behind a firewall or in a private network that is not connected to the internet.
 The key term of this definition is “private”. Only a limited number of users can access these resources. Using virtualization and distributed computing can allow administrators to create very complicated networks and datacenters that provide access to different services and resources for all the consumers from that network. All the information that flow on a private cloud is controlled by the administrators of that private cloud.
Physically, the private cloud doesn’t need to be on machines that are owned by the company. A private cloud can have 3 types of configuration:
  • All the physical machines are own and hosted by the client.
  • All the physical machines are in a public cloud (for example in Windows Azure). In this case the machines are in a private network that can be accessed only from that network.
  • A part of physical machine is from a private network of the client but also from a public cloud like Windows Azure. In this case a private network exists between all this machines. All the data that exist in this private network can be accessed only from the network.  
The properties of a private cloud should be the following:
  • Scalable
  • Shared
  • Elastic implementation
  • Automated
From what we saw, a private network can have different configuration. The networks that form the private cloud (computing resources, data and so on) have limited access. Only from that private network this resources can be accessed and consume. The customer has the control and ownership of all the content regardless of location. The provider of this services offer limited access to this resources – only for the client that need the private cloud.

Comments

  1. Another "definition" of private cloud would be: "I am a very, very large enterprise, I want to use Azure, but I don't want to host my app on Microsoft datacenters" - now I can go to Fujitsu or HP with my Azure apps.. ;)
    (desi unii zis ca "private cloud" ar fi o contradictie in termeni: http://news.cnet.com/8301-13556_3-10150841-61.html)

    ReplyDelete
    Replies
    1. sorry for my romenglish :)
      (although some said that "private cloud" is a contradiction in terms: http://news.cnet.com/8301-13556_3-10150841-61.html)

      Delete

Post a Comment

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills)

Cloud Myths: Cloud is Cheaper (Pill 1 of 5 / Cloud Pills) The idea that moving to the cloud reduces the costs is a common misconception. The cloud infrastructure provides flexibility, scalability, and better CAPEX, but it does not guarantee lower costs without proper optimisation and management of the cloud services and infrastructure. Idle and unused resources, overprovisioning, oversize databases, and unnecessary data transfer can increase running costs. The regional pricing mode, multi-cloud complexity, and cost variety add extra complexity to the cost function. Cloud adoption without a cost governance strategy can result in unexpected expenses. Improper usage, combined with a pay-as-you-go model, can result in a nightmare for business stakeholders who cannot track and manage the monthly costs. Cloud-native services such as AI services, managed databases, and analytics platforms are powerful, provide out-of-the-shelve capabilities, and increase business agility and innovation. H...

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...