How FlowTrace works

The browser registers a user input via the operating system input pipeline.

A synthetic event is dispatched through the DOM event system to listeners.

JavaScript invokes the handler, runs validation and prepares the payload.

Client state is updated optimistically before the network call resolves.

The fetch call serializes the payload into an HTTP request with headers.

The hostname is resolved through a recursive DNS query to an IP address.

Client and server negotiate ciphers and exchange keys to encrypt the channel.

The request hits the nearest edge node which may serve cached assets.

The gateway routes the request, applies rate limits and forwards to services.

Middleware verifies the session token, scopes and permissions.

The controller orchestrates business logic and downstream calls.

A hot key is checked in the in-memory cache to avoid hitting the database.

A background job is enqueued for asynchronous processing.

A transaction writes the record using a parameterized SQL statement.

The server serializes the result and streams it back over the same connection.

React reconciles the virtual DOM and the browser paints the next frame.