A blog post with a link to an example project here

A set of abstractions allowing you to implement event sourcing projections with offset tracking and most importantly a way to handle failures gracefully.

If you are using only CQRS without the event store you could still use Aperture to make your life easier.

Currently offset tracking and event stream adapters are implemented for:

• PostgreSQL

To come:

• MSSQL
• EventStore

These adapters come pre built (some in core some in adapter packages), but aperture is easily extensible (adheres to ports and adapters style of architecture) and allows you to create your own event stream/store, offset tracking, projection, failure strategy, exception handling and logging adapters.

Offset tracking adapters and Projection adapters are deliberately segregated so you can be as flexible as you wan't.

You can for example use Postgres adapters to both track your projection state (offset) and use sql projection to ensure your offset and read model are saved in a transaction.

If you don't care about offset tracking you could use built-in no op offset tracker (which always starts from 0) and still use sql projection adapter.

Or use any other combination of offset tracking and projection adapters
(including your custom built ones).

• Bulk projections (smth like buffered streams with Flush)
• Ability to define retriable exceptions instead of retrying all ProjectionExceptions
• LRU for pull event stream?
• Expose API or Web Dashboard