Google Git
Sign in
apache / aries-journaled-events / refs/heads/dependabot/maven/junit-junit-4.13.1
commit43dc478350d90a9ccb0446d3d551022203145f80[log] [tgz]
authordependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>Thu Jul 20 17:20:54 2023 +0000
committerGitHub <noreply@github.com>Thu Jul 20 17:20:54 2023 +0000
treeed56e5135f9bc886d1f9c903f0b758245e55281f
parentc297a412e9d865f4f914ee389ea8905474caf5bd [diff]
Bump junit:junit from 4.12 to 4.13.1

Bumps [junit:junit](https://github.com/junit-team/junit4) from 4.12 to 4.13.1.
- [Release notes](https://github.com/junit-team/junit4/releases)
- [Changelog](https://github.com/junit-team/junit4/blob/main/doc/ReleaseNotes4.12.md)
- [Commits](https://github.com/junit-team/junit4/compare/r4.12...r4.13.1)

---
updated-dependencies:
- dependency-name: junit:junit
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
1 file changed
tree: ed56e5135f9bc886d1f9c903f0b758245e55281f
  1. org.apache.aries.events.api/
  2. org.apache.aries.events.kafka/
  3. org.apache.aries.events.memory/
  4. org.apache.aries.events.mongo/
  5. .gitignore
  6. .travis.yml
  7. LICENSE
  8. pom.xml
  9. Readme.md
Readme.md

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