Skip to main content

Who is manage what in cloud (IaaS, PaaS, SaaS)

I expect that all of us heard about IaaS (Infrastructure as a Service), PaaS (Platform as a Service), SaaS (Software as a Service). Nothing special with this, especially in a cloud environment.
Pretty often I discover that the responsibility of the cloud provider and the customer are not very clear. Generally, we expect to have minimum responsibilities when we are using SaaS. In the same time when we are using IaaS we expect to have almost the same control as for On-Premises. But, this is not all the time true.
Let's take the main component of an environment and see who is the responsible for it in Azure - the customer or Microsoft Azure.

Network - The responsibility of the this component is 100% on Microsoft Azure on all the environments (IaaS, PaaS, SaaS). Azure is offering and manage the network where we have our system.
Storage - Similar with Network, this is a component that is manage fully by Azure. From blob storage, to OS images and VM disks, the cloud providers needs to manage and control it. We have only a small degree of configuration that we can do.
Servers - All servers that exist in Azure are managed and control by them (from the hardware perspective). Even for IaaS, we don't have any control at the hardware level.
Virtualization - Lucky, for all environments (IaaS, PaaS, SaaS), the virtualization is managed by Azure. We don't need and want to handle hardware virtualization by our self, especially on cloud.

Until now all the responsibility was on Azure. From now, the responsibility can be on customer part also.

OS - For PaaS and SaaS, the responsibility is on the cloud provider. But, for IaaS, the customer has the full control and can decide what kind of OS wants and can manage the OS by himself.
Middleware - As for OS, the responsibility is at customer level for IaaS and is full managed by Azure for PaaS and SaaS.
Runtime - You can control the runtime only if you have access at OS and Middleware. Because of this this is full managed by cloud provider for PaaS and SaaS. For IaaS, the customer can manage and control it.
Data - Starting with data, more responsibility is on customer side. Only for SaaS environment, the data is managed by Azure. For PaaS and IaaS, the customer has control and the responsibility to manage it.
Applications - For IaaS and PaaS, each customer has the freedom to install any application on the environment that he use. Only for SaaS, you don't have the ability to install any custom application.

As we can see above, Azure fully manage and control Network, Storage, Servers and Virtualization. We only need to manage the layers that are above virtualization, from OS to Applications, based on our needs and type of cloud provider that we are using


Popular posts from this blog

How to check in AngularJS if a service was register or not

There are cases when you need to check in a service or a controller was register in AngularJS.
For example a valid use case is when you have the same implementation running on multiple application. In this case, you may want to intercept the HTTP provider and add a custom step there. This step don’t needs to run on all the application, only in the one where the service exist and register.
A solution for this case would be to have a flag in the configuration that specify this. In the core you would have an IF that would check the value of this flag.
Another solution is to check if a specific service was register in AngularJS or not. If the service was register that you would execute your own logic.
To check if a service was register or not in AngularJS container you need to call the ‘has’ method of ‘inhector’. It will return TRUE if the service was register.
if ($injector.has('httpInterceptorService')) { $httpProvider.interceptors.push('httpInterceptorService&#…

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 …

[Post-Event] Codecamp Conference Cluj-Napoca - Nov 19, 2016

Last day I was invited to another Codecamp Conference, that took place in Cluj-Napoca. Like other Codecamp Conferences, the event was very big, with more than 1.000 participants and 70 sessions. There were 10 tracks in parallel, so it was pretty hard to decide at  what session you want to join.
It was great to join this conference and I hope that you discovered something new during the conference.
At this event I talked about Azure IoT Hub and how we can use it to connect devices from the field. I had a lot of demos using Raspberry PI 3 and Simplelink SensorTag. Most of the samples were written in C++ and Node.JS and people were impressed that even if we are using Microsoft technologies, we are not limited to C# and .NET. World and Microsoft are changing so fast. Just looking and Azure IoT Hub and new features that were launched and I'm pressed (Jobs, Methods, Device Twin).
On backend my demos covered Stream Analytics, Event Hub, Azure Object Storage and DocumentDB.

What abo…