Infra Cloud Service Platform (ICSP)
summary
A single platform layer provides a declarative YAML-based config repo called the service configuration graph with validation and dry-run and change diffs that are code-reviewable, backed by a central control plane where domain-specific controllers actuate routing, deployment and autoscaling and write state back. A formal service data model encodes topology and multi-tenancy (tenants 12–14 example, tenants 1–4 shared vs tenant 5 isolated) and a policy called config as data replaces ad-hoc scripts. Domain APIs, facets for actor lineage, and incremental onramp aim for broad rollout over 3–5 years and are already in testing.
AI-written summary · about
chapters (10)
- 0:00ICSP introduction
- 2:57Problem and ICSP role
- 6:30High-level design
- 8:35Control plane and APIs
- 10:45Service data model
- 14:38Private vs public cloud
- 16:02Config changes and graph
- 19:54Multi-tenancy in ICSP
- 21:58AI platforms with ICSP
- 22:41Future outlook
related talks
35mBuilding a sovereign, vendor-agnostic Cloud API
40m“So, where do you put IaC of your services?”
06mIGNITE: Unleashing the Magic: Building SaaS Platforms
24mSelf-Service Multi-Cloud K8s Platform at a Regulated Financial Enterprise
49mPublic cloud in regulated industry, not just swipe of a cred
55mSelf-service infrastructure is no longer a dream
16mThe Sovereignty Blueprint: Multi-Cloud Platform Strategy for European Ecosystem
33mOpen Cloud Services and an Open Cloud Computing Stack