tfredrich / domain-eventing Goto Github PK

Currently, if the JVM is stopped before processing is complete, messages are dropped. Add capability to persist events to disk to enable durable eventing.

Tests fail on CloudBees Jenkins jobs due to much lower I/O capability (evidently). Need to increase wait times/timeout values so tests don't fail.

Would be nice if we could get to see a sample implementation with this library. The namings are good enough to be self-explanatory, still an working example will give us insight into the design intentions and can help us rid of assumptions

Enable configuration to be passed in that creates clustered Actors.

Scale out even handling via new actors instead of using Executor.

Consider using Akka for messaging both within and across JVMs.

Possibly enhance Domain-Eventing library with the capability of eventing across machines instead of simply within the VM. Perhaps leverage HazelCast ( http://www.hazelcast.com/ ) or leverage vert.x ( http://vertx.io/ ).

EventHandlerActor has no way to raise exceptions in processing to the event bus. Possibly support dead-letter queue, retry, or dead letter.

Does this library support clustered deployment.