Danilo Cianfrone

Closed as #231 already partially addressed the content of this PR.

Hey @pwoolcoc, thanks for opening the issue! For a new backend implementation, you need to implement the following traits: 1. [`EventStore`](https://ar3s3ru.github.io/eventually-rs/eventually/store/trait.EventStore.html), for appending and streaming events on request 1. [`EventSubscriber`](https://ar3s3ru.github.io/eventually-rs/eventually/subscription/trait.EventSubscriber.html),...

Hey @pwoolcoc, if you're still interested in adding this feature, you can check out #128 for reference: it adds support for Redis backend.

Hey @pwoolcoc :wave: Feel free to open a PR to have the CI tests run :smile:

Also, now that I've created an org for `eventually`, I was considering moving `eventually-postgres` and `eventually-rust` out in their own respective repositories in the org. Maybe we can do the...

Hey @pseudo-su :wave: Yes, initially the example app was running using Postgres. However, since it's hard to test many of the components in the crate, I wrote integration tests targeting...

Hey @taqtiqa-mark, thank you for reporting this 🙇🏻‍♂️ I think more documentation is always better. We can definitely add more information in a relevant README.md file 👍🏻 I cannot spot...

Hey @zamazan4ik, thanks for the issue! I really like DynamoDB and I think it would make for a great Event Store. Also, it comes with natively supported Change Data Capture...

Hi @d4h0 and @AngelicosPhosphoros :wave: Thank you for posting the issue! @d4h0: it might be possible to put everything in a single file, however that file might be a tad...

Previously that was the case: the app was part of the repo. However, at some point the dependencies for the example app broke, and it completely broke compilation of the...