Skip to content
Browse files
Some ideas for goals and requirements
  • Loading branch information
cschneider committed Dec 31, 2018
1 parent f0da77e commit f71aaa91cf13a2e6a08140a20e18d8b2a08e4106
Showing 1 changed file with 18 additions and 0 deletions.
@@ -1,3 +1,21 @@
# Apache Aries Journaled events

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

0 comments on commit f71aaa9

Please sign in to comment.