Grooves

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.

Modules

grooves-groovy	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.
grooves-java	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.
grooves-api	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.
grooves-types	This contains types that are used in grooves-api. It is very unlikely you’ll be using this directly.
grooves-diagrams	This is an asciidoctor extension that allows you to generate diagrams like those in grooves' documentation.

Examples

grooves-example-springboot-jpa	This uses Springboot and JPA repositories for everything. All the code is written in groovy.
grooves-example-springboot-kotlin	This uses Spring Reactive Web and RxMongo repositories for everything. All the code is written in kotlin.
grooves-example-javaee	This uses Java and JavaEE for the APIs. The persistence here is completely made up using a few List objects. The reason for that is to show how you don’t have to be tied to any one persistence mechanism.
grooves-example-pushstyle	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.

Releasing

• Tag to release. A GitHub action should take care of publishing. Remember to update grooves-site/versions.json with the correct list of supported versions.