LogoLogo
  • Firehose
  • Introduction
    • Firehose Overview
    • Prerequisites
  • Architecture
    • Components
      • Firehose-enabled Node
      • Reader
      • Merger
      • Relayer
      • gRPC Server
      • High Availability
    • Data Flow
    • Data Storage
  • Firehose Setup
    • Overview
    • Ethereum
      • Installation
      • Single-Machine Deployment
      • Reprocessing history
      • Synchronization
    • Injective
      • Single-Machine Deployment
    • NEAR
      • Single-Machine Deployment
    • Solana
      • Single-machine Deployment
    • System Requirements
  • Community Integrations
    • Starknet
      • Networks and nodes
      • Local deployment with Docker
      • Local deployment without Docker
  • Integrate New Chains
    • Benefits
    • Integration overview
    • Design Principles
    • Firehose Acme
  • References
    • Supported Protocols
    • Naming Conventions
    • Schemas
    • Indexing
    • FAQ
  • Release Notes
    • Change logs
      • Nov 8th 2023 Polygon Update
Powered by GitBook
On this page
  • gRPC Server Component in Detail
  • Historical Data
  • Live Data
  • Relayer & Reader Coordination
  • Serving Data

Was this helpful?

Edit on GitHub
  1. Architecture
  2. Components

gRPC Server

StreamingFast Firehose gRPC server component

gRPC Server Component in Detail

The Firehose gRPC Server component is responsible for providing the extracted, formed, and collated blockchain data handled by the other Firehose components.

Historical Data

Firehose will use merged blocks from data storage directly for historical requests.

Live Data

Live blocks are received from the Relayer component.

Relayer & Reader Coordination

The Relayer component gets its data from one, or more, Reader components.

Serving Data

The Firehose gRPC Server component provides the data to the end consumer of Firehose through remote method calls to the server.

PreviousRelayerNextHigh Availability

Last updated 2 years ago

Was this helpful?