The message body.
The runtime handle the queue is resolved from.
Reports whether the capability is actually usable on this runtime.
The runtime handle.
true when calls will reach a real backing resource.
A capability backed by an optional resource answers false when that
resource was never provisioned. Implementations must document what each
method does in that state — degrade or throw — and must not vary it, since
a caller choosing between two implementations is relying on the answer
meaning the same thing in both.
A producer that hands work to something else to finish later.
Remarks
Producing only. Consuming is an entrypoint concern — the runtime delivers a batch to a handler rather than the application asking for one — so it is not expressible as a method here and does not belong on this interface.
Enqueueing returns a boolean rather than throwing because the work is by definition not what the caller is waiting on: the request that triggered it should still succeed when the follow-up could not be scheduled, and the caller decides whether that is worth logging. An unavailable queue reports
falsefor the same reason.Author
Bayu Dwiyan Satria
Version
1.0.0
Since
1.0.0