Spring Cloud Stream Reactor support. #572
Conversation
| @@ -971,6 +971,17 @@ initializr: | |||
| versionRange: 1.3.0.RELEASE | |||
| groupId: org.springframework.cloud | |||
| artifactId: spring-cloud-stream-binder-kafka | |||
| - name: Stream Reactor | |||
| id: cloud-stream-reactive | |||
| description: Messaging microservices with Reactor. Typically used with a Spring Cloud Stream binder implementation. | |||
There was a problem hiding this comment.
Typically used with a Spring Cloud Stream binder implementation.
What does that mean. Does this work standalone or does this require another dependency?
There was a problem hiding this comment.
it requires another dependency. You must choose a Spring Cloud Stream binder implementation like Kafka or RabbitMQ
| - name: Stream Reactor | ||
| id: cloud-stream-reactive | ||
| description: Messaging microservices with Reactor. Typically used with a Spring Cloud Stream binder implementation. | ||
| versionRange: 1.3.0.RELEASE |
There was a problem hiding this comment.
I don't understand. What's "fishy"?
| - rel: reference | ||
| href: https://docs.spring.io/spring-cloud-stream/docs/current/reference/htmlsingle/#_reactive_programming_support | ||
| description: Reactive Programming support for Spring Cloud Stream | ||
|
|
There was a problem hiding this comment.
I'd like a reference to a sample that demonstrates what you can do with this.
There was a problem hiding this comment.
Here ya go. In a normal Spring Cloud Stream application I can say
@StreamListener("incomingMessageChannel")
public void incoming( Message<String> msg) {
// handle a new message
}
or:
@StreamListener("incomingMessageChannel")
public void incoming( String msg) {
// handle a new message
}
and messages will be delivered to the handler method from whatever message broker you've specified in choosing your Spring Cloud Stream binder. With the new support represented by this checkbox, we can have the incoming values delivered as a Reactor Flux<T>. Your method is called once and all values are delivered as new values in the Flux<T> stream. This makes it trivial to do things like windowing over values, and integrating with other reactive Publisher<T> types (such as those that WebClient produces).
snicoll
added
the
status: waiting-for-feedback
|
Duplicate of #557 |
snicoll
added
status: duplicate
and removed
status: waiting-for-feedback
|
@joshlong we already discussed this entry in another issue you've created. |
import models only when they exist
Adds support for the reactor spring cloud stream binder.