Quine is a streaming graph interpreter; a server-side program that consumes data, builds it into a stateful graph structure, and runs live computation on that graph to answer questions or compute results. Those results stream out in real-time.

You interact with Quine by connecting it to a data source (Kafka, Kinesis Data Stream, SQS, files, stdin, etc.) and using regular database queries to stream that data in, build the graph structure, and find important patterns.

Three design choices define Quine, setting it apart from all event stream processing systems:

1. A graph-structured data model
2. An asynchronous actor-based graph computational model
3. Standing queries

Standing queries live inside the graph and automatically propagate the incremental results computed from both historical data and new streaming data. Once matches are found, standing queries trigger actions using those results (e.g., execute code, transform other data in the graph, publish data to another system like Apache Kafka or Kinesis).

All together, Quine can:

• Consume high-volume streaming event data
• Convert it into durable, versioned, connected data
• Monitor that connected data for complex structures or values
• Trigger arbitrary computation on the event of each match

This collection of capabilities is profoundly powerful! It represents a complete system for stateful event-driven arbitrary computation in a platform scalable to any size of data or desired throughput.

Read the docs at quine.io to learn more.

In order to build Quine locally, you'll need to have the following installed:

• A recent version of the Java Development Kit (17 or newer)
• The sbt build tool
• Yarn 0.22.0 (for frontend components of quine-browser subproject)

Then:

sbt compile           # compile all projects
sbt test              # compile and run all projects' tests
sbt fixall            # reformat and lint all source files
sbt quine/run         # to build and run Quine
sbt quine/assembly    # assemble Quine into a jar 

Run Quine from an executable .jar file built from this repo or downloaded from the repo releases page.

❯ java -jar quine-x.x.x.jar -h
Quine universal program
Usage: quine [options]

  -W, --disable-web-service
                           disable Quine web service
  -p, --port <value>       web service port (default is 8080)
  -r, --recipe name, file, or URL
                           follow the specified recipe
  -x, --recipe-value key=value
                           recipe parameter substitution
  --force-config           disable recipe configuration defaults
  --no-delete              disable deleting data file when process exits
  -h, --help
  -v, --version            print Quine program version

For example, to run the Wikipedia page ingest getting started recipe:

❯ java -jar quine-x.x.x.jar -r wikipedia

With Docker installed, run Quine from Docker Hub.

❯ docker run -p 8080:8080 thatdot/quine

The quick start guide will get you up and running the first time, ingesting data, and submitting your first query.

Quine recipes are a great way to get started developing with Quine. A recipe is a document that contains all the information necessary for Quine to execute any data processing task. Ingest data from batch sources like .json or .csv files hosted locally, or connect to streaming data sources from Kafka or Kinesis.

Recipes are yaml documents containing the configuration for components including:

• Ingest Streams to read streaming data from sources and update graph data
• Standing Queries to transform graph data, and to produce aggregates and other outputs
• UI configuration to specialize the web user interface for the use-case that is the subject of the Recipe

Please see Quine's Recipe repository for a list of available Recipes. Or create your own and contribute it back to the community for others to use.

The community is the heart of all open-source projects. We welcome contributions from all people and strive to build a welcoming and open community of contributors, users, participants, speakers, and lurkers. Everyone is welcome.

More information is included in our contribution guidelines.