Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

RabbitMQ Streams as an event store

Abierto
  • ¿Algo no está bien?
#432 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 7 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Estancado
Stack tecnológico
csharp, rabbitmq
Área
backend

Línea de trabajo

Start by reading the RabbitMQ Streams and Superstreams documentation linked in the issue, then inspect the repository’s event store integrations and entry points for adding a new store. The issue proposes two storage models but does not specify the API, scope, or acceptance criteria; done would require defining and implementing how aggregates are stored and replayed through RabbitMQ Streams.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

In many architectures, RabbitMQ is used as a messaging layer, but event sourcing or replay capabilities are offloaded to a separate event store (e.g. EventStoreDB, MongoDB, PostgreSQL, Microsoft SQL Server). It would be advantageous if RabbitMQ itself could act as the event store so that producers/consumers can leverage one unified system with replay, retention, partitioning, etc.

Describe the solution you’d like

I propose a feature where RabbitMQ Streams can serve as a first-class event store.

The idea is that instead of having RabbitMQ just as a message broker and then pushing events into an external event store, the stream layer of RabbitMQ becomes the event store itself.

Options:
  1. One RabbitMQ Stream per aggregate instance (e.g., Booking-{bookingId})
  2. One RabbitMQ Superstream per aggregate type, partitioned by aggregate instance
    • Superstream: Booking
    • Partition key = bookingId
Describe alternatives you’ve considered

Keep the current pattern: use RabbitMQ for messaging, and integrate with a separate event store (e.g. Microsoft SQL Server).

Additional context

RabbitMQ Streams already supports many of the low-level features needed: non-destructive reads, replay, offsets, partitioned super-streams, etc.

The “Streams and Superstreams” documentation: https://www.rabbitmq.com/docs/streams

Lenguaje dominante
C#
Estrellas
512
Forks
99
Merge medio
5 d 6 h
PR fusionados (30 d)
5

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Eventuous/eventuous

Todos los issues de Eventuous/eventuous

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.