Nebula
Persistence

PersistenceAnswer

Whether the answer a store is delivering right now is a stand-in for one the backend could not give.

generated from the sources
public static class PersistenceAnswer

Whether the answer a store is delivering right now is a stand-in for one the backend could not give.

Every read and every IPersistenceStore.WhenWritten is answered exactly once, even when the backend fails for good (a store gives up on a job after a few attempts). A read it could not answer gets the empty result — a null record, an empty list, an empty entry per container, a count of 0 — and a barrier is released, after the store has logged the error. While such a callback runs, Failed is true, so a caller that must not mistake "unreadable" for "nothing saved" can tell them apart. The orchestrator's PersistenceHost answers those requests with HTTP 503, and the worker retries.

Properties

Failed

public static bool Failed { get; }

True only inside a store callback whose answer is a stand-in for a failed backend call.

Methods

Invoke

public static void Invoke(Action callback, bool failed);

Run callback with Failed set to failed. For store implementations.

On this page