Skip to content

FormSpec Architecture

Status: Draft License: Creative Commons CC0

Dokumen arsitektur menjelaskan bagaimana FormSpec berjalan di production — topology deployment, resource registration, failover, K8s operator, dan admin surfaces. Dokumen ini bersifat deskriptif/penjelasan, bukan normatif. Spec normatif tetap di docs/spec/.

Untuk fitur, desain internal, dan API tiap komponen runtime secara individual (FormSpec Control, FormSpec Resource, FormSpec Operator, FormSpec Sidecar), lihat docs/runtimes/. Untuk referensi CLI (formspec, formspec-ctl), lihat docs/cli-tools/.


Document Map

01-architecture-overview.md   ← Mulai dari sini
02-admin-surfaces.md          ← Tiga admin UI + pemiliknya
03-deployment-flow.md         ← Pipeline: formspec apply → deploy → run
04-resource-registration.md   ← Server, DB, Valkey lifecycle
05-failover.md                ← HA, auto-failover, recovery
06-k8s-operator.md            ← FormSpec Operator, CRD, ClusterClass
07-vertical-modules.md        ← ERP module division: verticals/, App/Workspace composition, branch model
08-repo-structure.md          ← Struktur folder repo FormSpec, lensa spec-vs-renderer (untuk kontributor codebase)
09-domain-map.md              ← Peta subdomain formspec.dev, DNS, hosting, email

Reading Paths

🏗️ App Developer

OrderDocument
101-architecture-overview.md — Where does my app run?
203-deployment-flow.md — How does formspec apply work in production?

🖥️ Platform Operator

OrderDocument
101-architecture-overview.md — Full topology
204-resource-registration.md — Server, DB, Valkey registration
305-failover.md — HA and auto-failover
406-k8s-operator.md — FormSpec Operator + ClusterClass

👤 Workspace Owner

OrderDocument
101-architecture-overview.md — Regions, ClusterClass, tiers
202-admin-surfaces.md — formspec/console features

🏢 ERP Vertical Author

OrderDocument
107-vertical-modules.md — Module taxonomy, App/Workspace composition, branch model, ERPNext comparison

🧑‍💻 Framework Contributor

OrderDocument
108-repo-structure.md — Peta folder repo, pemetaan kode ↔ dokumen spec/renderer, kesenjangan implementasi

Architecture Decisions Index

Semua keputusan desain arsitektur tercatat sebagai D-ARCH-1 sampai D-ARCH-31 di 01-architecture-overview.md. Component inventory ada di §2. Deployment model (satu pipeline, generic image) ada di §3.


Relationship to Spec Documents

Architecture DocRelated Spec
01-architecture-overview.md01-overview.md §5–§6, 04-control-plane.md
02-admin-surfaces.mdspec/frontend/01-visual-hierarchy.md §1
03-deployment-flow.mdspec/platform/05-plane-protocol.md §0
04-resource-registration.mdspec/platform/06-datastore.md, 04-control-plane.md
05-failover.mdspec/platform/05-plane-protocol.md §1
06-k8s-operator.mdspec/platform/03-kind-system.md
07-vertical-modules.mdspec/platform/02-workspace-app-module.md §1/§3, spec/backend/01-core-basic.md §5, docs/comparison/formspec-vs-frappe.md
08-repo-structure.mddocs/spec/README.md (prinsip contract-vs-renderer), docs/spec/platform/08-project-layout.md

Standar terbuka (CC0) dengan implementasi referensi.