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.


  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:

    1. sorry for my romenglish :)
      (although some said that "private cloud" is a contradiction in terms:


Post a Comment

Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…