Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Event Sourcing for Rust

License

NotificationsYou must be signed in to change notification settings

get-eventually/eventually-rs

Repository files navigation


Eventually

Event Sourcing for Rust

GitHub Workflow StatusCodecovCrates.iolatest main docsdocs.rs docsGitHub license

Collection of traits and other utilities to help you build your Event-sourced applications in Rust.

Installation

⚠️v0.5.0 is under active development: Breaking changes are expected. If you are usingeventually as a git dependency you should use a pinned version!

Addeventually into your project dependencies:

[dependencies]eventually = {version ="0.5.0",features = ["full"],git ="https://github.com/get-eventually/eventually-rs" }

Note on semantic versioning

This library isactively being developed, and prior tov1 release the followingSemantic versioningis being adopted:

  • Breaking changes are tagged with a newMINOR release
  • New features, patches and documentation are tagged with a newPATCH release

What is Event Sourcing?

Before diving into the crate's internals, you may be wondering what Event Sourcing is.

Fromeventstore.com introduction:

Event Sourcing is an architectural pattern that is gaining popularity as a method for building modern systems. Unlike traditional databases which only store and update the current state of data, event-sourced systems store all changes as an immutable series of events in the order that they occurred and current state is derived from that event log.

How doeseventually-rs support Event Sourcing?

eventually exposes all the necessary abstraction to model yourDomain Entities (in lingo,Aggregates) using Domain Events, andto save these Events using anEvent Store (the append-only event log).

For more information,check out the crate documentation.

You can also take a look at thebank-accounting example,showcasing Event-sourced application for a generic (and simple) Bank Accounting bounded context.

Event Store backends

eventually-rs provides the necessary abstractions for modeling and interactingwith an Event Store.

These are the following officially-supported backend implementations:

Contributing

You want to contribute toeventually-rs but you don't know where to start?

First of all, thank you for considering contributing ❤️

You can head over ourCONTRIBUTING section to knowhow to contribute to the project, and — in case you don't have a clear idea whatto contribute — what is most needed needed from contributors.

License

This project is licensed under theMIT license.

Contribution

Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion ineventually-rs by you, shall be licensed as MIT, without any additional terms or conditions.


[8]ページ先頭

©2009-2025 Movatter.jp