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

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

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 http://go.microsoft.com/fwlink/?LinkId=260882 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.51 EF 6.0.2 VS2013 It see

Navigating Cloud Strategy after Azure Central US Region Outage

 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too