CatalystVisual

05 Lifecycle

SDK Client Read-Path Lifecycle

The states a long-lived SDK client moves through, and why a failed flag check degrades instead of raising.

Construction performs no I/O. Every check then reads conditionally and decides locally. When the API is unreachable the client opens a time-based backoff window and keeps serving the last good snapshot, because a flag check usually sits inside somebody else's request and must not turn into a 500.

What to look for

  • Backoff is the recoverable failure: the window is time-based, so the read path always resumes.
  • Rejected is the one terminal state, because a key that was revoked will not become valid again.
  • This is the only diagram here that is slightly taller than a 900px viewport when opened on its own.