System Topology
How Laputa's microservices talk to each other
This map shows the control-plane path from the public portal through events, workflows, provisioning, and facility services. Click any node to inspect how it participates in the platform.
Read This First
Solid conversations are synchronous control calls. Dashed and dotted flows show eventing, status fan-out, and infrastructure-side operations.
The key boundary in the current architecture: NestJS publishes intent, FastAPI owns deployment orchestration, and Spring owns physical database lifecycle.
What it does
- Consumes deployment/delete events from NestJS.
- Provisions marketplace databases, kicks off workflows, and applies tenant resources.
Inbound
FastAPI consumes application events and turns them into deployment workflows.
Outbound
FastAPI starts Dapr workflows to coordinate deploy, verify, and rollback behavior.
FastAPI calls Spring to provision or deprovision marketplace databases during deploy/delete flows.
Immediate request/response calls from the portal or controller layer.
Event-driven transitions that reduce direct coupling between services.
Message backbone and status fan-out through Dapr and NATS.
Provisioning, rollout verification, and image/database lifecycle edges.