Architectural decision
Edge/control plane differs from the application data plane
Ingress and coordination are different from canonical records and domain commands.
Before · Conflated concepts
Cloudflare EdgeNext.js OriginFirestoreFirebase Auth
After · Explicit boundaries
Relationships
- Cloudflare Edge forwards admitted requests to Next.js Origin
Problem and decision
Provider names alone obscure which runtime actually owns application work.
Use Cloudflare for edge/control-plane roles and Firebase/Google Cloud for identity, data and Node-capable workloads.
Alternatives considered
- Move every workload to the edge
- Make the origin own all edge concerns
Tradeoffs and consequences
A provider boundary adds integration and release coordination.
Next.js on Cloud Run remains distinct from edge delivery and canonical persistence.
Related architecture
Related workflows
Current architectural direction; this record does not establish production release.