There was an error while loading. Please reload this page.
The current Firebolt native client exposes synchronous APIs while internally utilizing an asynchronous JSON-RPC transport.
+-------------+ | Application | +-------------+ | v +-------------------+ | Firebolt Client | +-------------------+ | v +--------------------+ | Firebolt Transport | +--------------------+ | v +------------------+ | Firebolt Server | +------------------+ ## Request Lifecycle * Application invokes API. * Gateway creates Promise. * Promise stored using JSON-RPC request ID. * Request sent to Firebolt Server. * Response received. * Promise resolved. * Result returned to caller. ## Gateway Responsibilities * JSON-RPC request generation * Response correlation * Promise lifecycle management * Timeout management * Watchdog processing