Pattern ◆◇◇◇◇ IN.001
Docker Port Mapping
Map container ports to host ports to expose services while maintaining network isolation between containers.
Open detail chart → Domain chart · iv
Infrastructure
the Platform Frontier
Microservices orchestration, container platforms, infrastructure as code, and CI/CD pipeline design for resilient production systems.
Celestial position
Featured visualisation — kubernetes orchestration topology
Declarative Platform
The Control Plane declares desired state; worker nodes converge to it. API Server is the single authority — every other component subscribes. Pods are ephemeral; the scheduler places them; etcd stores ground truth.
control plane — api server, scheduler, controller manager
etcd — authoritative cluster state store
worker nodes — kubelet + pods
service / ingress — load-balancing & routing
Featured visualisation — gitops deploy & drift reconciliation
GitOps Pipeline Flow
A commit triggers CI build, image push to the registry, and a declarative K8s apply — each mote represents an artifact propagating through the pipeline. A second lane traces drift detection: when actual state diverges, the reconciler pulls desired state back to convergence.
deploy pipeline — git → ci → registry → k8s apply
health check — readiness probe passes
drift detection — actual→desired reconciliation
Featured visualisation — microservices service mesh
Service Mesh Topology
Each service exposes a well-defined interface; the mesh routes, load-balances, and observes traffic between them. A degraded Payments service (amber, dashed ring) triggers circuit-breaker pulses — upstream services continue while the downstream recovers. Motes trace live inter-service calls.
healthy service — nominal traffic
data store — persistent state boundary
degraded service — circuit breaker active
Featured visualisation — ci/cd delivery pipeline & quality gates
CI/CD Delivery Pipeline
Every commit flows through six quality gates: Source → Build → Test → Security Scan → Deploy → Health Check. Approximately one in five artifacts fails the Test gate — these bounce down to a retry lane, returning to Build before attempting the gate again. A green pulse marks each successful health check.
artifact · moving through pipeline stages
health check · successful deploy
test gate failure · deflected to retry
retry token · returns via build lane
Featured visualisation — gitops reconciliation loop
GitOps Reconciliation
The operator polls the Git repository as the single source of truth. Commit tokens flow Git Repo → Operator → Apply → Cluster → Drift Check. When drift is detected — actual state diverging from desired — the mote deflects down the reconciliation lane back to the operator, which re-applies until the cluster converges. Convergence emits a green pulse.
commit token — desired state from git repo
apply — k8s manifest propagating to cluster
converged — actual state matches desired
drift detected — reconciliation loop triggered
Skill progression — Infrastructure Architecture
Platform Proficiency
Declarative infrastructure and controlled isolation enable increasingly sophisticated orchestration. Select a node to inspect.
Skill progression4 / 6
Select a skill to inspect
Pattern catalogue — Infrastructure
Pattern ◆◆◆◆◇ IN.002
Multi-Database Orchestration
Coordinate multiple purpose-fit databases within a single system, routing reads and writes to the appropriate store.
Open detail chart → Principle ◆◆◇◇◇ IN.003
Infrastructure as Code
Define and provision infrastructure declaratively through versioned configuration, enabling reproducible environments.
Open detail chart →