Sign in

Tags / Backend and APIs /

Event sourcing

A library or framework that stores application state as a sequence of events, often with CQRS.

The 29repositories with this Tag gained +54 net stars in the last 30 days, 7% less than the 30 days before.

0 created in the last 90 days · 5 published a release in the last 30 days · 29K stars in total

All in the Repository Index On Trending

Net stars each day, last 30 days+16 last 7 days

Oct 6, 2026Nov 4, 2026

Most net stars, last 30 days

kurrent-io/KurrentDB

KurrentDB is a database that's engineered for modern software applications and event-driven architectures. Its event-native design simplifies data modeling and preserves data integrity while the integrated streaming engine solves distributed messaging challenges and ensures data consistency.

+20

37% of the net stars of this Tag

Largest Pace, last 30 days

No other repository gained 2 or more times the net stars of the 30 days before.

Most stars, created in the last 90 days

No other repository with this Tag was created in the last 90 days.

Where the stars went, last 13 weeks

Net stars gained each week. The repositories that gained the most have their own color.

kurrent-io/KurrentDB gained 33% of the net stars of this Tag in the last 13 weeks.

kurrent-io/KurrentDB, week to Aug 12: +10 net starsJasperFx/marten, week to Aug 12: +3 net starscommanded/commanded, week to Aug 12: +4 net starsAll other repositories, week to Aug 12: +7 net starskurrent-io/KurrentDB, week to Aug 19: +9 net starsJasperFx/marten, week to Aug 19: +5 net starspyeventsourcing/eventsourcing, week to Aug 19: +2 net starscommanded/commanded, week to Aug 19: +1 net starsAll other repositories, week to Aug 19: +5 net starskurrent-io/KurrentDB, week to Aug 26: +2 net starsJasperFx/marten, week to Aug 26: +4 net starspyeventsourcing/eventsourcing, week to Aug 26: +2 net starsRailsEventStore/rails_event_store, week to Aug 26: +4 net starskurrent-io/KurrentDB, week to Sep 2: +1 net starsJasperFx/marten, week to Sep 2: +4 net starscommanded/commanded, week to Sep 2: +1 net starsRailsEventStore/rails_event_store, week to Sep 2: +3 net starsAll other repositories, week to Sep 2: +2 net starskurrent-io/KurrentDB, week to Sep 9: +3 net starsJasperFx/marten, week to Sep 9: +1 net starspyeventsourcing/eventsourcing, week to Sep 9: +2 net starsAll other repositories, week to Sep 9: +1 net starskurrent-io/KurrentDB, week to Sep 16: +2 net starsJasperFx/marten, week to Sep 16: +2 net starsAll other repositories, week to Sep 16: +1 net starskurrent-io/KurrentDB, week to Sep 23: +5 net starsJasperFx/marten, week to Sep 23: +1 net starspyeventsourcing/eventsourcing, week to Sep 23: +2 net starscommanded/commanded, week to Sep 23: +1 net starsRailsEventStore/rails_event_store, week to Sep 23: +1 net starsAll other repositories, week to Sep 23: +7 net starskurrent-io/KurrentDB, week to Sep 30: +3 net starsJasperFx/marten, week to Sep 30: +5 net starspyeventsourcing/eventsourcing, week to Sep 30: +2 net starscommanded/commanded, week to Sep 30: +2 net starsAll other repositories, week to Sep 30: +4 net starskurrent-io/KurrentDB, week to Oct 7: +10 net starsJasperFx/marten, week to Oct 7: +8 net starscommanded/commanded, week to Oct 7: +2 net starsAll other repositories, week to Oct 7: +11 net starskurrent-io/KurrentDB, week to Oct 14: +5 net starsJasperFx/marten, week to Oct 14: +1 net starspyeventsourcing/eventsourcing, week to Oct 14: +5 net starsAll other repositories, week to Oct 14: +3 net starskurrent-io/KurrentDB, week to Oct 21: +2 net starsJasperFx/marten, week to Oct 21: +3 net starscommanded/commanded, week to Oct 21: +1 net starsRailsEventStore/rails_event_store, week to Oct 21: +1 net starsAll other repositories, week to Oct 21: +1 net starskurrent-io/KurrentDB, week to Oct 28: +3 net starsJasperFx/marten, week to Oct 28: +1 net starscommanded/commanded, week to Oct 28: +1 net starskurrent-io/KurrentDB, week to Nov 4: +7 net starsJasperFx/marten, week to Nov 4: +1 net starspyeventsourcing/eventsourcing, week to Nov 4: +2 net starsRailsEventStore/rails_event_store, week to Nov 4: +1 net starsAll other repositories, week to Nov 4: +6 net stars

Compare growth

0 of 29 repositories: Created on GitHub in the last 90 days. Select a column name to change the order.

No repository with this Tag is in this view for the last 90 days.

Faster than the 30 days before

Net stars of the last 30 days are 2 or more times those of the 30 days before.

No repository with this Tag meets this rule now.

Slower than the 30 days before

Net stars of the last 30 days are 50% or less of those of the 30 days before.

No repository with this Tag meets this rule now.

New in the last 90 days

Created on GitHub in the last 90 days.

No repository with this Tag meets this rule now.

Older than 2 years, still releasing

Created more than 2 years ago, with a push in the last 7 days and a GitHub release in the last 30 days.

  1. kurrent-io/KurrentDB5.9K · release 9 days ago
  2. JasperFx/marten3.5K · release 3 days ago
  3. boostercloud/booster447 · release 7 days ago
  4. Ahoo-Wang/Wow306 · release 3 days ago

Last release more than 180 days ago

The newest GitHub release is more than 180 days old. A repository that never published a release is not in this list.

  1. eventflow/EventFlow2.6K · release 11 months ago
  2. message-db/message-db1.7K · release 4 years ago
  3. ElderJames/shriek-fx652 · release 8 years ago
  4. prooph/event-store545 · release last year
  5. SQLStreamStore/SQLStreamStore467 · release 8 years ago
All 9 in the table

How a repository gets this Tag

An agent reads the description, the GitHub topics, and the start of the README of each repository. It chooses Tags only from the Tag list in the AwesomeRepos source code. For each Tag, it quotes the text. A code check keeps the Tag only when the quote is in that text. The page of each repository shows the quote of each of its Tags. A Tag does not rank repositories. It does not say that one repository can replace another. To report a wrong Tag, use "Report a problem with this page" on the page of the repository.

How the numbers are counted

All numbers come from the Star History of the repositories that have the Tag now. A period is a run of complete UTC days. All numbers on this page count only the repositories that AwesomeRepos shows in lists. A machine computes them each hour.

For each repository, a period counts only when Star History has each of its days, or when the repository was created in the period. Otherwise the table shows "–". The bars of a week with no complete data are grey.

The Pace is the net stars of a period divided by the net stars of the period before. It shows only when Star History covers each day of the period before, with at least 3 net stars a day on average.

The chart at the top adds up the net stars of all the repositories with the Tag. A rising Admission comes into the Repository Index because it gained stars quickly. Its Star History before its Admission comes from the Repository Host. Thus the days before many rising Admissions are higher than they were for the repositories in the index at that time.

The releases are the GitHub releases of each repository. The lists and the table do not rank repositories, and they do not say that one repository can replace another.