https://github.com/apache/aries-journaled-events
Apache aries
https://github.com/apache/aries-journaled-events
aries java library
Last synced: 9 months ago
JSON representation
Apache aries
- Host: GitHub
- URL: https://github.com/apache/aries-journaled-events
- Owner: apache
- License: apache-2.0
- Created: 2018-12-30T09:34:20.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2023-09-05T21:57:45.000Z (almost 3 years ago)
- Last Synced: 2025-10-14T00:17:13.581Z (9 months ago)
- Topics: aries, java, library
- Language: Java
- Homepage: https://aries.apache.org/
- Size: 120 KB
- Stars: 1
- Watchers: 12
- Forks: 7
- Open Issues: 4
-
Metadata Files:
- Readme: Readme.md
- License: LICENSE
Awesome Lists containing this project
README
# Apache Aries Journaled events
Jenkins: [](https://builds.apache.org/job/Aries-journaled-events/)
Travis: [](https://travis-ci.org/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