file-ipc-patterns

File-based interprocess communication enables separate Python services to exchange requests, state, and live events using the filesystem. It leverages JSONL append-only logging and atomic file replacement to safely sync processes without introducing a message broker.

Atomic state snapshots maintain a current state.json file that remains complete and safe to read during updates. This technique uses atomic file replacement to ensure concurrent processes never encounter partially written state data.

Yes, filesystem events can be mirrored to SSE subscribers for streaming dashboards and session monitoring. This pattern bridges JSONL append-only logs and state updates into live event streams for long-running task visibility.

Async request-response via files involves creating request files and resolving them with matching response payloads. It bridges the result back to running asyncio code using safe request-id validation and thread-safe Future resolution.

Yes, filesystem interprocess communication applies directly to host-and-container workflows. By exchanging JSONL logs and atomic state files across shared volumes, separate processes can coordinate requests and events without network dependencies.

JSONL append-only logging provides a replayable event history and supports tail-friendly live updates. This format allows multiple processes to safely append events to a shared file for interprocess communication without locking conflicts.