sim-orchestrator

You can orchestrate Neo4j, Kafka, and FastAPI services for a digital twin simulation by running a centralized app that applies deterministic startup sequencing and readiness probes to coordinate booting and data seeding. This ensures predictable convergence across all services.

Seeding day-one data and starting a virtual clock for an airport twin is handled through scenario-driven injections during the initialization sequence. The orchestrator waits for service readiness, seeds the airport structure, and then drives the virtual clock.

Yes, you can use Docker Compose to boot the simulation clock and domain services. Running the FastAPI app with uvicorn or using the repository's Docker Compose setup initializes the ecosystem and starts the virtual clock.

Restart convergence and snapshot restore work by applying resilience checks and readiness probes before safe restarts. The orchestrator ensures predictable convergence by monitoring service health and restoring snapshots to maintain simulation state.

You monitor tick processing and simulation events for observability through exposed metrics endpoints and structured logs. These features track tick processing speed and simulation events to ensure system health during orchestration.