daggerok/es

Event Sourcing... sometimes... maybe...

es

Read project reference documentation

es system

 +-----+
 |  e  |
 |  s  |
 |     |                      +-------------+       messaging     +-------------------+
 |  e  |      messaging       | es commands |-+    <----------    | +-----------+     |-+
 |  v  |     <----------      +-------------+ |       http        | | es client | App | |-+
 |  e  |                        +-------------+      <---->       | +-----------+     | | |-+
 |  n  |                                                          +-------------------+ | | |-+
 |  t  |    http (on boot)    +------------+                        +-------------------+ | | |
 |     |   <-------------->   | es queries |-+        http            +-------------------+ | |
 |  s  |      messaging       +------------+ |-+     <---->             +-------------------+ |
 |  t  |     ---------->        +------------+ |                          +-------------------+
 |  o  |                          +------------+
 |  r  |
 |  e  |
 +-----+

TODO

1. Implement es-event-store: First implementation could be: event-store-postgresql or event-store-h2

   • for beginning could be just enough to use:

     1. http post for commands

     2. http get for queries right out from the event-store (inefficient)

2. …​

build

./gradlew clean publish build documentation ; ./mvnw clean deploy install -Pdocs

Initially generated by using generator-jvm yeoman generator (java-parent-multi-project)