---
type: "ABB"
nummer: "ABB-0601"
abb_id: "ABB-0601"
abb_nummer: "MD03"
naam: "Source Code Repo-as-a-Service"
archimate_type: "Grouping"
laag: "Managed Diensten"
auteur: "E. Kuik"
status: "Niet vermeld"
gerelateerde_adrs: ["ADR-G60"]
archimate_element: "id-30232"
archimate_grouping: "id-30232"
archimate_technology_service: ["id-30233"]
archimate_view: "id-29948"
ontwerp_paragraaf: "5.6.1"
ontwerp_link: "../../input/markdown/NDS%20Overheidsbrede%20Soevereine%20Clouddienst%20Ontwerp%20v0.9.md#positionering-managed-diensten"
ontwerp_paragrafen: ["4.5", "5.6.1"]
ontwerp_links:
  - "../../input/markdown/NDS%20Overheidsbrede%20Soevereine%20Clouddienst%20Ontwerp%20v0.9.md#selfserviceportaal-soevereine-paas-dienst"
  - "../../input/markdown/NDS%20Overheidsbrede%20Soevereine%20Clouddienst%20Ontwerp%20v0.9.md#positionering-managed-diensten"
---

# ABB-0601: Source Code Repo-as-a-Service

```mermaid
%%{init: {"flowchart": {"nodeSpacing": 12, "rankSpacing": 12, "padding": 8}}}%%
flowchart TB
    %% id-30207 -> id-30244 (Grouping)
    subgraph v_id_30207["Managed SaaS"]
        direction TB
        %% id-30209 -> id-30249 (Grouping)
        subgraph v_id_30209["ABB: SIEM-as-a-Service"]
            direction TB
            %% id-30211 -> id-30250 (TechnologyService)
            v_id_30211["SIEM-as-a-Service"]
        end
        %% id-30213 -> id-30246 (Grouping)
        subgraph v_id_30213["ABB: IAM-as-a-Service"]
            direction TB
            %% id-30215 -> id-30247 (TechnologyService)
            v_id_30215["IAM-as-a-Service"]
        end
    end
    %% id-30181 -> id-30224 (Grouping)
    subgraph v_id_30181["Managed PaaS"]
        direction TB
        %% id-30187 -> id-30235 (Grouping)
        subgraph v_id_30187["ABB: Infra-as-Code-as-a-Service"]
            direction TB
            %% id-30189 -> id-30236 (TechnologyService)
            v_id_30189["Infra-as-Code-as-a-Service"]
        end
        %% id-30203 -> id-30232 (Grouping)
        subgraph v_id_30203["ABB: Source Code Repo-as-a-Service"]
            direction TB
            %% id-30205 -> id-30233 (TechnologyService)
            v_id_30205["Source Code Repo-as-a-Service"]
        end
        %% id-30183 -> id-30229 (Grouping)
        subgraph v_id_30183["ABB: Backup &amp; Restore-as-Service"]
            direction TB
            %% id-30185 -> id-30230 (TechnologyService)
            v_id_30185["Backup &amp; Restore-as-Service"]
        end
        %% id-30195 -> id-30238 (Grouping)
        subgraph v_id_30195["ABB: Database-as-a-Service"]
            direction TB
            %% id-30197 -> id-30239 (TechnologyService)
            v_id_30197["Database-as-a-Service"]
        end
        %% id-30191 -> id-30226 (Grouping)
        subgraph v_id_30191["ABB: Message Queue-as-a-Service"]
            direction TB
            %% id-30193 -> id-30227 (TechnologyService)
            v_id_30193["Message Queue-as-a-Service"]
        end
        %% id-30199 -> id-30241 (Grouping)
        subgraph v_id_30199["ABB: CI/CD-as-a-Service"]
            direction TB
            %% id-30201 -> id-30242 (TechnologyService)
            v_id_30201["CI/CD-as-a-Service"]
        end
    end
    %% id-30177 -> id-30221 (Grouping)
    subgraph v_id_30177["ABB: Tenant Cluster Data Plane-as-a-Service"]
        direction TB
        %% id-30179 -> id-30222 (TechnologyService)
        v_id_30179["Tenant Cluster Data Plane-as-a-Service"]
    end
    v_id_30179 -->|Serving| v_id_30181
    v_id_30179 -->|Serving| v_id_30207
    style v_id_30211 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30209 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
    style v_id_30215 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30213 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
    style v_id_30207 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
    style v_id_30189 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30187 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
    style v_id_30205 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30203 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
    style v_id_30185 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30183 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
    style v_id_30197 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30195 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
    style v_id_30193 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30191 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
    style v_id_30201 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30199 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
    style v_id_30181 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
    style v_id_30179 fill:#d6f8b8,stroke:#000000,color:#111111
    style v_id_30177 fill:#ffffff,stroke:#585858,color:#111111,stroke-dasharray:4 3
```

## Selfserviceportaal Soevereine PaaS Dienst

Het product Selfserviceportaal Soevereine PaaS Dienst is strikt genomen geen onderdeel van Het Ontwerp (zie 1.9 Scope) maar is hier opgenomen voor een heldere duiding en demarcatie van de soevereine hostingproducten.

![Figuur 4‑4 Decompositie Selfserviceportaal Soevereine PaaS Dienst](<../../input/markdown/media/media/image13.svg>)

Het Selfserviceportaal voorziet in meerdere partijen die PaaS-producten gaan leveren gebruikmakend van het product Soevereine Cloud-native Hosting. Omdat het om PaaS gaat, zal zo'n partij typisch gebruikmaken van het Tenantcluster van de afnemer van het PaaS-product. De technologiediensten gemodelleer*d* in *Figuur 4‑4 Decompositie Selfserviceportaal Soevereine PaaS Dienst,* zijn voorbeelden en vormen geen uitputtende opsomming.

## Positionering Managed Diensten

Managed diensten vallen uiteen in PaaS-diensten die typisch in het tenantcluster van de PaaS-afnemer worden gehost en SaaS-diensten die in het tenantcluster van de SaaS-aanbieder (dus niet tenantcluster van de afnemer) worden gehost.

![Figuur 5‑21 Positionering Managed Diensten](<../../input/markdown/media/media/image51.svg>)

Samenvatting uitgangspunten, architectuurkeuzes en aandachtspunten:

- Interface voor infra-as-code zou typisch via zowel een GUI (handmatig) als API (t.b.v. geautomatiseerde uitrol van applicaties) kunnen worden aangeboden
