Skip to content

Commit

Permalink
Update docs/bos/queryapi/how-works.md
Browse files Browse the repository at this point in the history
Co-authored-by: Morgan McCauley <morgan@mccauley.co.nz>
  • Loading branch information
bucanero and morgsmccauley authored Sep 7, 2023
1 parent dcc2b7b commit beef96e
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/bos/queryapi/how-works.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ An in-depth, detailed overview of the QueryApi components:

- **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 executes developer's JS code.
- **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.
- **Database**: a Postgres database where filtered and indexed results are stored, using a Logical DB per user, and a Logical schema per indexer function.
- **API**: a Hasura GraphQL server running on Google Cloud Platform exposes simple web API endpoints so users can access GraphQL queries and subscriptions from anywhere.

Expand Down

0 comments on commit beef96e

Please sign in to comment.