Event Sourcing Library for Java.
Grooves formerly meant Groovy Event Sourcing. In its present form, it can support just about any JVM language. Examples and tests include Java, Groovy and Kotlin. Documentation can be found here.
A much simplified way of building Event-Sourced queries. This is the newer way of building queries.
This contains types that are used in grooves-api
.
It is very unlikely you’ll be using this directly.
This is for you if you are not using groovy or java, or don’t care about verifying completeness of queries. For example, you could use this for writing code with Kotlin.
This is for you if you want to write your queries in groovy, but are not using GORM. You will have to implement your own data access, but will get support for checking completeness of queries based on groovy AST Transformations.
This is for you if you want to write your queries in java. You will have to implement your own data access, but will get support for checking completeness of queries based on Annotation Processors.
This uses Springboot and JPA repositories for everything. All the code is written in groovy. |
|
This uses Spring Reactive Web and RxMongo repositories for everything. All the code is written in kotlin. |
|
This uses Java and JavaEE for the APIs.
The persistence here is completely made up using a few |
|
This uses Kotlin and Guava EventBus. The snapshots are persisted using jOOQ. The events are never persisted. They are processed as they come on the EventBus. |