How QueryAPI works

QueryApi is a streaming indexer implementation that executes custom indexing logic written by developers on the NEAR blockchain.
QueryApi allows hosted execution of complex queries (ones that can’t be answered by a simple RPC or Enhanced API call), data hosting, and its exposure via GraphQL endpoints.

Components involved

The QueryApi implementation integrates many different components in a single and streamlined solution.

In a high-level overview, the main components are:

::info Components
NEAR Protocol -> NEAR Lake -> Coordinator -> Runner -> Database -> API

::

Detailed overview

An in-depth, detailed overview of the QueryApi components:

Description

• Protocol: the underlying NEAR Layer-1 Blockchain, where data Blocks and Chunks are produced.
• NEAR Lake: an indexer which watches the Layer-1 network and stores all the events as JSON files on AWS S3. Changes are indexed as new Blocks arrive.
• Coordinator: the QueryApi coordinator indexer filters matching data Blocks, runs historical processing threads, and queues developer’s JS code to be indexed with these matched blocks.
• Runner: executes the user’s indexer code, which outputs the data to the database.
• Database: a Postgres database where the developer’s indexer data is stored, using a logical DB per user, and a logical schema per indexer function.
• API: a Hasura server running on Google Cloud Platform exposes a GraphQL endpoint so users can access their data from anywhere.

Who hosts QueryAPI

Pagoda Inc. runs and manages all the infrastructure of QueryAPI, including NEAR Lake nodes to store the data in JSON format on AWS S3.

• NEAR Lake indexing is hosted on AWS S3 buckets.
• Coordinator is hosted on GCP.
• Runners are hosted on AWS SQS and AWS Lambda.
• Hasura GraphQL API server is hosted on GCP.

:::caution Pricing

QueryAPI is currently free. Pagoda doesn’t charge for storage of your indexer code and data as well as running the indexer, but usage pricing will be introduced once QueryApi is out of beta.

::