liveBook · Manning

Fire-and-forget operation

A fire-and-forget operation is work initiated without the caller waiting for or consuming its completion, result, or response.

How 2 Manning books explain it

F# in Action: A Revised Edition of Get Programming with F#

A fire-and-forget operation is an asynchronous operation started without awaiting or otherwise consuming its completion or result.

How it is used
Uses background asynchronous work when callers need neither an immediate response nor a returned result.
How deep it goes
Defines no-result Tasks and task-state inspection, but does not detail fire-and-forget lifecycle management.
Examples
Uses background order processing, file writing, delayed Tasks, and asynchronous file reading as examples.
What you can do after
Evaluate task progress and failure by inspecting Status, completion flags, and Exception.

Read how F# in Action: A Revised Edition of Get Programming with F# explains fire-and-forget operation →

Spring in Action, Sixth Edition

The fire-and-forget model is a communication pattern in which a client sends a request without receiving a response from the server.

How it is used
Uses RSocket when a client must send data without receiving a server response.
How deep it goes
Explains the interaction model and demonstrates a reactive server handler and client call, without detailing delivery guarantees.
Examples
Uses a starship red alert, an Alert payload, an alert route, and logging as concrete examples.
What you can do after
Apply it via Spring RSocket by mapping a Mono<Void> handler and calling send() without retrieving a response.

Read how Spring in Action, Sixth Edition explains fire-and-forget operation →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.