Skip to content

docs(server): design horizontal scale-out over centralized data stores #427

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
davidwkeith merged 1 commit into from
Jul 24, 2026
Merged

docs(server): design horizontal scale-out over centralized data stores #427

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion spec/portability.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -242,7 +242,10 @@ SQLite/file-backed shims and the single-writer lockfile invariant (and GCS
FUSE is not safe for SQLite). A native host would mean Firestore- or
Cloud-SQL-backed shims (Firestore is strongly consistent with transactions,
so it passes the consistency bar) — again a large rewrite. The pragmatic
answer is the Docker image on a GCE VM.
answer is the Docker image on a GCE VM — or, once the proposed scale-out
mode ([scale-out.md](scale-out.md)) lands, the same image on Cloud Run with
centralized stores, since that design removes exactly the two blockers named
here (local-disk state and the single-writer lockfile).

### 4.5 Puter — revisit later

Expand Down
Loading
Loading