Skip to content

index.md

Latest commit

 

History

History
49 lines (36 loc) · 2.57 KB

index.md

File metadata and controls

49 lines (36 loc) · 2.57 KB
Raw

Architecture

docs / Architecture

Audiences: all

System architecture and design decisions for ML Deployment Toolkit -- an infrastructure-agnostic Mojaloop distribution. The platform uses an optional Tooling Cluster for shared services (OCI registry, secrets, object storage) and one or more App Environment clusters for Mojaloop workloads.

How these documents fit together

flowchart TD
    overview["System Overview\n(delivery pipeline, cluster roles,\nconfiguration system)"]

    overview --> provider["Provider Model\n(infrastructure providers,\nmanaged vs self-hosted)"]
    overview --> gitops["GitOps Structure\n(OCI artifact,\nkustomization hierarchy)"]
    overview --> networking["Networking\n(Gateway API, 3-LB,\nDNS strategy)"]
    overview --> security["Security\n(Vault isolation model,\nrecovery kit)"]
    overview --> data["Data Layer\n(databases, backup,\ndisaster recovery)"]
    overview --> observability["Observability\n(metrics, logs, traces,\ndashboards)"]

    networking --> mtls["DFSP mTLS\n(PKI model, inbound/outbound,\nCA rotation)"]
    security --> mtls
    provider --> networking
    mtls --> dfspint["DFSP Integration\n(tenancy boundary,\nDFSP-side stack)"]
    networking --> dfspint
Loading

Documents

Document Description
System Overview Delivery pipeline, cluster roles, deployment stages
Provider Model Infrastructure providers, managed vs self-hosted, Cilium strategy
GitOps Structure OCI artifact, kustomization hierarchy, Flux wiring
Networking Gateway API, 3-LB architecture, DNS strategy
DFSP mTLS PKI model, inbound/outbound mTLS, Vault Agent, CA rotation
DFSP Integration Tenancy boundary, DFSP-side Helm chart topology, config and cert bootstrap
Security Vault isolation model, security layers, recovery kit
Observability Metrics (Thanos), logs (Loki), traces (Tempo), dashboards
Data Layer Databases, backup architecture, disaster recovery

Decision records

Design decisions are recorded as individual ADRs in decisions/. Each record captures the context, alternatives considered, and consequences of a non-obvious design choice. Records are append-only -- a superseded decision gets a status update, not a deletion.

Looking for procedures?

For procedures (how to build, deploy, operate), see the audience-specific guides linked from the docs index.