cilly
  • Notes
  • OSS
  • About
  • Life
  • Contact

Architecture Notes

Firebase / GCP

Architecture diagram: contract.yml as the single source of truth, compiled through an IR into per-layer code

Generating every Firebase layer’s types from a single contract.yml

Structurally eliminating the drift of maintaining the same model across Data Connect, Firestore, Zod, and API DTOs, with code generation from a YAML contract as the single source of truth.

2026-07-19
Architecture diagram of the Platform Sync pipeline

Syncing what comes after provisioning — Cloudflare DNS, Logto, cert-gated proxy, env bundles

The design of a CI pipeline that keeps DNS, auth, delivery certificates, and env values — everything left over after config-driven GCP / Firebase provisioning — following the same source of truth.

2026-06-30
Architecture diagram of the multi-environment GCP / Firebase platform

Provisioning GCP / Firebase environments from a single settings.yml

The design of a platform that chains GCP project creation through Firebase setup, keyless, with a per-service settings file as the source of truth.

2026-06-24
Runtime architecture and data flow

Runtime and delivery of a multi-service Firebase environment

A development environment with multiple services sharing one GCP project, presented through two cross-sections: how it runs (runtime) and how it ships (delivery).

2026-06-24
Firebase / GCP

Treating Firestore as a public cache

The design benefits — and the costs — that come into view when Cloud SQL is the source of truth and Firestore is a read-optimized projection.

2026-05-27

© 2026 cilly

  • Source
  • GitHub