![[photo-1484253292651-6e940b0a0e26.jpg]] Photo by [jesse orrico](https://unsplash.com/@jessedo81?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) on [Unsplash](https://unsplash.com/photos/ZazRf32F5Pg?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) The "Spheres" Multi-tenancy reference model offers great combination of sharing and isolation at all XaaS levels (vertically) and building blocks (horizontally). The reference model consists from XaaS category connected to particular Shared Level and associated with particular Multi-tenant model and Isolation Level. A combined Shared and Isolation level characterizes Multi-tenancy level for each XaaS Component. Let’s take a look at the Score Overview below ![[Pasted image 20230709114125.png|Figure 1: multi-tenancy reference model]] ## DCaaS (Data Center as a Service) Model represents Physical structure of Data Center Inputs: - Security – Building and Departments Security Management - Governance – DC Operations Management - Network – Main Dedicated Connection (Telco Provider) - Utilities: - Power – Energy for Building Operations and Computing - Water for Building Operations, AC and Computing cooling Systems - Air for Building Operations, AC and Computing cooling Systems - People – DC Staff Residing in Building Office ![[Pasted image 20230709114150.png|Figure 2: DCaaS]] Multi-tenancy description for DC Building blocks: - Bandwidth Meters (Management) – Shared for all connections - Utilities Meters (Management) – Shared for all utilities - Offices (Operation Management) – Shared for all Operations and Customers - Fire Suppression Systems (Management) – Shared for all locations - UPS + Generator (Backup Management) – Shared for all Systems - Air Conditioning (Temperature Management) – Shared for all locations - Access Management - Shared on Building Level, Isolated on Location and Customer Levels ## IaaS (Infrastructure as a Service) Model represents Physical structure of Deployed Infrastructure Inputs: - Security – Physical Infrastructure Security (Rack) - Governance – Management of Infrastructure Deployment, Upgrades etc. - Network – Limited Connection/Bandwidth based on SLA - Power for Infrastructure Components within Rack ![[Pasted image 20230709114211.png|Figure 3: IaaS]] Multi-tenancy description for Infrastructure Building blocks: - Network Switch – Shared for Rack Components, Isolated per Network or Customer - LAN – Shared, Isolated per Customer - WAN – Shared - Wi-Fi – Shared among Customers within DC Facility - Fibre Channel - Shared - Storage Switch – Shared , Isolated for HA Configurations - SAN – Shared, Isolated for HA Configurations - RAID – Isolated on Customer / Array Level - DAS – Shared, Isolated for HA Configurations - NAS – Shared, Isolated for HA Configurations - Server – Shared, Isolated per Customer - Server Bus, Cache – Shared - Server Storage and Network Interfaces – Shared , Isolated per Customer - CPU – Isolated per Customer on core or thread level - Memory – Shared on CPU level, Isolated per Customer ## PaaS (Platform as a Service) Model represents Software and Platform Foundations Inputs: - Security – Security Management of Platforms - Governance – Platform Management - Network – Software Networks - Data – Platform related Data - Users – Platform Users ![[Pasted image 20230709114246.png|Figure 4: PaaS]] Multi-tenancy description for Platform Building blocks: - Virtualization – Shared, isolated per customer, channel, virtual machine, network - OS – Shared, isolated per customer, virtual machine - File System – Shared, isolated per virtual machine, customer - Secure Protocol – Isolated per virtual machine, customer - Insecure Protocol – Shared - Internet – Shared - Extranet, Intranet, VPN – Isolated per customer - DMZ – Shared, Isolated per customer - Infrastructure Platforms – Fully Shared, Isolated per customer - Application platforms (represented by examples - not an exhaustive list) - Java – Shared on System level, isolated per customer and virtual machine - Cocoa - Shared on System level, isolated per customer and virtual machine - Flash / Flex – Shared on System level, isolated per customer and virtual machine - .Net - Shared on System level, isolated per customer and virtual machine - Other Application Platforms – Shared on Various levels , isolated per customer and virtual machine ## SaaS (Software as a Service) Model represents Software Inputs: - Security – Software Security Management - Governance – Software Management - Network – Software Networks - Data – Software related Data - Users – Software Users ![[Pasted image 20230709114324.png|Figure 5: SaaS]] Multi-tenancy description for Software Building blocks: - Wikis, Blogs – Fully Shared - Messaging – Shared , Isolated per customer, domain, channel - File Sharing – Isolated per Customer - Video Conference – Shared , Isolated for HA and Governance Solutions - WEB – Shared , Isolated for HA and Governance Solutions - Portal, Reporting, Channels – Shared, Isolated per Customer and for HA / Governance Solutions - CMS – Fully Isolated - Infrastructure, Security, Business Management - Fully Isolated per customer - Intrusion – Isolated per customer, channel - Encryption – Fully Shared - Business Intelligence, Packaged App – Shared, Isolated per customer - Database, Data warehouse - Isolated per customer - Perimeter – Shared, Isolated per customer and network - Anti-X – Fully Shared - SOA, Processing – Shared, Isolated per Customer - Communication – Shared, Isolated per Customer, Channel, Network ## DaaS (Data as a Service) Model represents Structured and Unstructured Data Inputs: - Security – Data Security - Governance – Data Management - Data: - Information - files and streams - Video – files and streams - Audio – files - Users – Data Users ![[Pasted image 20230709114346.png|Figure 6: DaaS]] Multi-tenancy description for Data Building blocks: - Audio, Video, Pictures, Binary, Unstructured Files, Structured Files, Information Streams – Shared, Isolated per Customer, Network, Channel - Alerts – Isolated per Customer, Network, Channel - Instant and Unified Messaging – Isolated per Customer, Network, Channel - Logs, Security Info - Isolated per Customer, Network, Channel, Business Segment, Domain, Application - Database – Shared on Schema Level, Isolated per Customer, Application - Repository – Shared per Domain, Isolated per Segment, Application - Metadata – Isolated per Customer ## BPaaS (Business Process as a Service) represents Business Processes Inputs: - Security – Business Process Security - Governance – Business Process Management - Data – Business Process related Data - Actors – Business Process Actors - Processes – Business Processes ![[Pasted image 20230709114422.png|Figure 7: BPaaS]] Multi-tenancy description for Business Process Building blocks: - Capabilities – are fully shared among all processes - Scenarios, Tasks, Processes, Use Cases – Shared, Isolated per Customer - Actors – are fully shared among all processes - Process Lifecycle, Process Map, Relationships, Time – Shared, Isolated per Customer - Business Rules – Shared, Isolated per Customer - Change Management, Re/Source Management, Performance Management – Shared, Isolated per Customer - Schedule – Shared, Isolated per Customer - Initiation Phase – Fully Shared - Modeling, Deployment, Termination Phase – Isolated per Customer - Simulation – Shared , Isolated per Customer - Future, Present, Past Views – Isolated per Customer ## INaaS (Industry as a Service) represents Industry Services Inputs: - Security – Industry Services Security - Governance – Industry Services Management - Data – Industry related Data - Actors – Industry Actors - Processes – Industry Processes ![[Pasted image 20230709114442.png|Figure 8: INaaS]] INaaS Model is great example of absolute sharing. It shares everything to everybody. This model is totally open in order to support business services and business processes. Industry networks are very similar to social networks – both are collaborative, the only difference is that industry networks are created by categorized business services , social networks are public or represents private communities. ## BaaS (Business as a Service) represents Business Services Inputs: - Security – Business Service Security - Governance – Business Service Management - Data – Business Information - Actors – Business Actors - Processes – Business Processes ![[Pasted image 20230709114501.png|Figure 9: BaaS]] Multi-tenancy description for Business Building blocks: - Service Management, Business Constraints – Shared, Isolated per Customer - Business Variables – Isolated per Customer (Business setup and differentiators) - Business Status – Shared - Business Vision, Business Strategy, Business Goal, Business Model, Business Tactic, Business Objective, Business Lifecycle, Business Principals, Business (Architecture) Differentiators – Shared, Isolated per Customer - Industry Type, Business Domain – Publicly shared for propagation and mediation purposes As a result, we connected dots between all (XaaS) multi-tenancy layers and identified several isolation spheres affecting (today) sharing levels and implementation of Business as a Service (BaaS) model (below). ![[Pasted image 20230709114526.png|Figure 10: Isolation Spheres]] ## Related to [[Absolute Multi-tenancy or The story about Massive Computing]]