📓
Live Content Cloud
  • LCC
  • Services
    • Infocaster
      • Deployment
      • API Docs
    • Query Streamer
      • Deployment
      • Architecture
      • API Docs
    • Native Push
      • Enable Huawei apps to receive push notifications
  • Support
    • Common issues
Powered by GitBook
On this page

Was this helpful?

  1. Services
  2. Query Streamer

Architecture

PreviousDeploymentNextAPI Docs

Last updated 3 years ago

Was this helpful?

Components

QS consists of the following parts:

  • ElasticSearch

  • Nodejs API

    • One CRUD API for handling client streams

    • One notify API for injecting events (from OC's notifier)

  • Multicaster Lambda

Elastic Search

The main reason we use Elastic Search is because of its . The percolator is sort of an "inverse database" in which you store quries and perculate documents to find all stored quires that that matches a specific document. For each stream that is created, a query is stored in the percolator together with two data objects, destination and meta.

The destination object describes how QS should publish the notification when a document matches the query.

For all supported destination types, go to the section below on the Notify API.

The Meta field can hold any meta data.

percolator feature