![[photo-1612345808274-f0e65dabf16e.jpg]] Photo by [FLY:D](https://unsplash.com/@flyd2069?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) on [Unsplash](https://unsplash.com/photos/u7OS4-5xLEs?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) There are usually two essential questions among architecture (and business) community around definition of XaaS (can it really represent any kind of service?) and how to approach pattern question related to #XaaS. Inside the first question, there is a slight distinction of terms between "**Everything as a Service**" and "**Anything as a Service**". First one [1] is assuming that everything eventually could be a service implying that Cloud Computing is extension of SOA principles [2] (Service Oriented Architectures) representing next step of IT Architecture evolution. However second explanation [3] leans towards business representation of cloud services and products with large cost savings over traditionally provided IT services and capabilities. As usual, explanation and representation of these services vary by each lens of the target audience and is broadly influenced by the NIST definition of Cloud Computing [4]. The trap positioned at the pattern question is relatively significant in comparison to previous one. It is prevalent and increasingly frequent to see architects pointing at the **Cloud Patterns** related to specific cloud layer or capability. Easy examples coming to mind are cloud migration patterns, integration pattern, streaming patterns and many more. ![[Pasted image 20230709103435.png|Figure 1: XaaS resources and composition]] However we believe that XaaS perception by different audiences should be simplified and visualized more holistically including associated patterns. There are couple of benefits making this proposition desirable: - avoid complexity of ever increasing XaaS categories / types with the need to draw them differently (separate layers or symbols) - embed unified dimensions into the patterns to standardize patterns composure across the XaaS categories - Governance, Actors, Processes, Data, Security, Network, Utilities, People, Time - align pattern visualization across all architectures with easy to understand and highly scalable #X2X method used by SPHERES architecture #framework. --- Let's take a look at standard enterprise representation of capability and service including internal composition (conceptual level). ![[Pasted image 20230709103455.png|Figure 2: Application, Platforms, Capabilities, Services layered inside Architecture tiers]] Simple, right? OK, now let's take a look at some pattern examples and their conceptual representation. ### IaaS ![[Pasted image 20230709103523.png|Figure 3: IaaS Concept]] ### **Capability and Foundational Platform** ![[Pasted image 20230709103545.png|Figure 4: Capability and Foundational Platform Concept]] Examples: Storage as a Service, Backup as a Service, DropBox, Database as a Service ### PaaS ![[Pasted image 20230709103603.png|Figure 5: PaaS Concept]] ### SaaS ![[Pasted image 20230709103623.png|Figure 6: SaaS Concept]] ### BPaaS ![[Pasted image 20230709103654.png|Figure 7: BPaaS Concept]] --- Now, let's try to summarize all visual pattern examples depicted above in one summary picture (below).  I'm sure a lot of you can see emerging visual patterns and you can start to see a light from this dark tunnel of architecture visualization exercise :) ![[Pasted image 20230709103856.png|Figure 8: XaaS visual patterns]] It's a great simplification (and perhaps a new perspective on the XaaS pattern visualization question), but we believe it's just a step away from the classic IT architecture (box and square) thinking and we have to advance further towards diametrically simplified way we understand and design cloud architecture tomorrow. By mixing services and capabilities we are free from rigorous XaaS definitions  (not helpful to business users) and still able to replicate blueprints of XaaS technical models (conceptually). And this is how we translate them to SPHERES XaaS patterns **SPHERES XaaS visual patterns** ![[Pasted image 20230709103920.png|Figure 9: SPHERES XaaS visual patterns]] Visualization technique and nomenclature above is truly universal and you can use it for any complex architecture by combining XaaS patterns into easy-to-understand "Everything as a service" or "Anything as a Service" (whatever works for you) model depicting relevant services and capabilities. We will discuss advanced visualization methods used by x2x model and SPHERES Patterns articles. ## References [1] WIKIPEDIA; EVERYTHING AS A SERVICE; https://simple.wikipedia.org/wiki/Everything_as_a_service [2] WIKIPEDIA; SOA; https://simple.wikipedia.org/wiki/Service_oriented_architecture [3] WIKIPEDIA; AS A SERVICE; https://en.wikipedia.org/wiki/As_a_service [4] PETER MELL; TIMOTHY GRANCE; NIST; THW NIST DEFINITION OF CLOUD COMPUTING; https://nvlpubs.nist.gov/nistpubs/Legacy/SP/nistspecialpublication800-145.pdf ## Related to [[Sharing and Isolation levels within Multi-tenancy reference model]]