Apache aries

Clone this repo:
  1. c297a41 Use HTTPS instead of HTTP to resolve dependencies (#22) by Jonathan Leitschuh · 3 months ago master
  2. 1ca1e23 Test PR by Christian Schneider · 1 year, 1 month ago
  3. e6b2780 Merge pull request #20 from cschneider/master by Christian Schneider · 1 year, 1 month ago
  4. eea6f81 Update Readme.md by Christian Schneider · 1 year, 1 month ago
  5. 1e68a30 Update Readme.md by Christian Schneider · 1 year, 1 month ago

Apache Aries Journaled events

Jenkins: Build Status Travis: Travis Build Status

This subproject provides an API (possibly as spec) and backends for journaled streams of events. These extend the publish/subscribe model with means to start consume from an point in the stored event stream history.

Goals

  • Provide traditional publish / subscribe semantics
  • Allow consuming a stream from any point in the history (given it is not yet evicted)

Non goals (to be discussed)

  • No coverage of extreme scaling like Apache Kafka. So no sharding support in the API (like partitions).

Requirements

  • Messages sent to a topic must be journaled and must be available to all consumers
  • Consumers must be able to start consuming messages from any point in the history that is still available
  • If a consumer specifies a position that is not available anymore then it must start with the oldest message
  • Each consumer must receive messages in the same order they were sent
  • The journal of each topic may evict messages that are older than a certain retention time