![[photo-1599394407175-b6da85464b90.jpg]] Photo by [Rachael Ren](https://unsplash.com/@ro_finity10969?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) on [Unsplash](https://unsplash.com/@ro_finity10969?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) Why Dimensions? Why can't we stick with tiers, layers, standard frameworks and categorizations , methods and simply use what we already have and know for decades? I'm sure, these questions are arising all the time (across the organization - not just architects) and for a good reason. Let's dive just a bit to a rationale behind dimensions used for ecosystem architecture in **conjunction with solution and enterprise architectures** we used up to now. --- Fundamentally, the **purpose of ecosystem architecture** is to design and preserve ecosystem in sustainable way. Sustainable; meaning dynamic in nature, capable to change quickly to prevent fail of mission critical components and agile enough to evolve and expand as needed. How do we architect systems today? We use #layers, #tiers and other techniques to combine structures together and connect them for dependence purposes. This is all good, but with increasing complexity of entities, quantity of solutions and XaaS models connected globally via APIs and MetaStructures - this method is no longer viable too encapsulate and understand behavior of higher level strategical and purpose build decision networks (i.e. AI, industrial clouds, multi-cloud BPaaS models, IoT, solution deployed beyond known geographical boundaries). We believe, Ecosystem Dimensions is the correct answer to enable identification of critical components spread-out across solutions, services and networks and combine them into unique perspective we call the "**Edge Sphere**". We will discuss the Edge Sphere and how to construct it from ecosystem dimensions at the sections below. > In physics and mathematics, the dimension of a mathematical space (or object) is informally defined as the minimum number of coordinates needed to specify any point within it. The inside of a cube, a cylinder or a sphere is three-dimensional (3D) because three coordinates are needed to locate a point within these spaces. The concept of dimension is not restricted to physical objects. [1] How many dimensions do we need? It is certainly a question with a lot of possible answers and theories behind shaped in dependency of the desired results. In example, 10 dimensions are used to describe superstring theory (6D hyperspace + 4D), 11 dimensions can describe supergravity and M-theory (7D hyperspace + 4D), and the state-space of quantum mechanics is an infinite-dimensional function space and we can go on... To simplify and make dimensions practical for ecosystem architecture and interaction, we propose simplified three dimensional architecture with further granularity of details integrating architecture layers (yes; the layers we are already using in solution and enterprise architectures). ![[Pasted image 20230709103021.png|Figure 1: 3D Dimensional Architecture]] Dimensions are combining technical , social, physical and business artifacts together by construction of three dimension categories: - #Solutions (Systems) - #Services (XaaS) - #Networks (Markets, Distribution and Communication) At the expanded picture below we can identify layers (or tiers) for each of the dimensions. ![[Pasted image 20230709103041.png|Figure 2: Layers (tiers) are high level components of single dimension]] Now comes the first major difference (in comparison to standard IT architectures) introduced by ecosystem dimensions: The **Critical Building Blocks**. We already discussed critical building blocks in previous articles, so just as a reminder - these are the entities (abstracts) identified as mission critical components of particular solution, service or network. > As an example, Critical building block might be Satellite connection for telco company; SAP cloud for Global Accounting company; internet connection for social networks; latency for multi-player games; sensor fields for weather condition networks; identification of patient for healthcare company and more. There are usually multiple (more than one) critical building blocks with the ecosystem, identifiable across all dimensions and layers inside. Combination of all critical building blocks within specific dimension enables allocation of "**Dimension Edge**" or we can call it critical dependency (integration) point. By application of this method to dimensions we can get "Solution Edges", "Service Edges" and "Network Edges". With combination of the Dimension #Edges (all three) into one model we can obtain a perspective on "**Edge Sphere**" as depicted below. ![[Pasted image 20230709103143.png|Figure 3: Integration of dimension edges into Edge Sphere]] Okay, now why do we need the Edge Sphere? First let's take a look at the picture below. The #EdgeSphere already contains all critical building blocks of particular ecosystem. These building blocks enables communication and interoperability between networks, services and solutions. Essentially, now you can see only what is important for survival (sustainability) of this ecosystem model. ![[Pasted image 20230709103211.png|Figure 4: Edge Sphere construction]] Building blocks captured in the Edge Sphere are critical components of Ecosystems (generally), therefore they are also critical for ecosystem lifecycle , expansion, value and more. More importantly, the Edge Sphere is a summary of all components needed to provide answers for monitoring , tracking, configuration and changes needed (predictions) represented by Ecosystem Viewpoints (take a look at "Ecosystem Architecture: Viewpoint" article to learn more). In summary, the Edge Sphere is a source of information (semantically based) for all SPHERES views. ![[Pasted image 20230709103230.png|Figure 5: Ecosystem viewpoints are directly dependent on Edge Sphere]] Edge building blocks (critical components identified inside dimensions) are also clearly identifiable at the level of **MetaData Structures** (diagram below) by highlighted dependency on multiple #MetaStructure boundaries. ![[Pasted image 20230709103253.png|Figure 6: MetaData Connection]] Let's put everything together and summarize the need for Ecosystem Dimensions and their crucial role in architecting, monitoring and changing ecosystems. Ecosystem critical components identified inside dimensions are shaping the Edge Sphere; as part of the Ecosystem; providing crucial viewpoint to Ecosystem health, parameters and capabilities. ![[Pasted image 20230709103314.png|Figure 7: 3D Architecture - The Map]] At the same time, these building blocks are identifiable as critical MetaData Structures enabling ecosystem component composition visible via different perspectives focused on target audience perception. Additionally, these Structures are shaping the **Blueprint (or DNA) of Ecosystems** in perhaps at first sight unusual way; but as we increasingly use these dimensions, we can replicate and build ecosystems without overwhelming complexity preventing their comprehensive understanding. ## References [1] WIKIPEDIA; DIMENSION; https://en.wikipedia.org/wiki/Dimension ## Related to [[Ecosystem Architecture - Patterns]] [[Ecosystem Architecture - Abstracts]] [[Ecosystem Architecture - Perspective vs Perception]] [[Ecosystem Architecture - The Viewpoints]]