reactive-commons-java
reactive-commons-java copied to clipboard
reactive-commons
Common abstractions for reactive microservices
Based on the in-memory message broker defined by Smallrye reactive messaging (https://smallrye.io/smallrye-reactive-messaging/smallrye-reactive-messaging/2/testing/testing.html) it would be nice to have a similar implementation as a utility for implementing integration tests without depending...
The connection with the broker and the message handling should be gracefully stopped. Today, When a spring application is shutdown, reactive commons keeps receiving messages and failing because other beans...
Assign retry delay to a message following some criteria, like exponential backoff
When a listenEvent is removed from the handler registry, the binding between the domainEvents and the subsEvents should be removed too
A handler with x.y.event should be invoked the same as x.y.# handler in the same application.
Bintray configuration is spread across many *.gradle files, we must centralize it in a single place ( bintray.gradle)
Inside Listeners, the types: RegisteredQueryHandler, RegisteredEventListener and RegisteredCommandHandler must have a single internal representation in order to centralize common behaviour.
Features: - Add kafka binding - Enable domain events with cloud events - Enable notification listener and event listeners
Metadata
Owner
Metadata
Common abstractions for reactive microservices