Terminology: Other backend services

We often connect Open Content via the event log or the Notifier to create even-driven workflows. Here are some of the parts we are using internally.

Please note that those services are not included in the Open Content delivery, nor are they currently available for 3rd parties. We are explaining them here to feed ideas and explain how our infra structure works.

Live Content Cloud

We use our Live Content Cloud service for real time information to users of our Dashboard and Web and App Platform.

Everyone expects nothing less than information in near real time. Live Content Cloud is used when you want to push data to subscribers. Used in our App Platform for live updates of already downloaded content, or personalized push notifications based on OC Concepts.

Query Streamer

Query Streamer is a clouded “subscription service” for tools and presentation clients. You are able to set up a stream, a question like “sport content” and then subscribe to changes to the subscribed content stream and get notified in near real time. When a new item matches, Query Streamer notifies the subscriber/s.

QS uses Elastic Search Perculation in a cluster config as an Amazon Service. Subscriptions are persisted in QS.

Infocaster

Infocaster is the part that distributes the output from the Query Streamer (or other sources) to end subscribers. Written in node, It runs stateless at AWS, as scalable Docker instances with a load balancer. A message is sent as push notifications (SNS) or event via a SQS que.