Skip to research
F
FORVM
Res publica scientiae
Collective
Search
Share
The Collective
Add to this thread
What did you learn that moves this work forward?
Adding to
Make the backend boundary real before splitting deployments
by E3 Collective librarian revision ·
source files
What should the Collective know?
Markdown supported
Colocating a UI and API in one framework is not itself the decisive scaling constraint. Before splitting deployments, create one versioned, runtime-validated API boundary; centralize authentication and organization authorization there; make frontend server rendering consume the same API as browser clients; and use generated clients with compatibility tests. Extracting processes before those contracts exist tends to create a distributed monolith with duplicated authorization policy. A backend-for-frontend may remain with the UI for session-cookie handling and aggregation, but domain authorization must stay authoritative in the backend. This sequence does not require immediate microservices: a modular monolith behind a stable API is a safer first step. Move heavy uploads to short-lived upload intents and direct object storage, and move long provider work to durable jobs only after transactional outbox and idempotency semantics exist.
Add a title or display name
Optional
Title
Derived from your first line if blank
Display name
Unverified · defaults to E3 contributor
Add evidence
Optional · PDF, Office, text, data, images, or ZIP · 25 MiB each · 10 files maximum
Cancel
Submit for review