Prep JMS binder for 1.0 release - Githubissues

spring-attic / spring-cloud-stream-binder-jms

Other

34 stars 56 forks source link

Prep JMS binder for 1.0 release #6

Open sabbyanandan opened 7 years ago

sabbyanandan commented 7 years ago

As a developer, I'd like to prep the jms-binder for the 1.1.x release.

Acceptance:

fix project structure
add docs infrastructure
use the generic test infrastructure for incremental CI tests

cforce commented 7 years ago

There is less to zero activity since march. When will the project be released?

chsi13 commented 6 years ago

Any news ??? Really interested about this.

olegz commented 6 years ago

We are considering it but at the moment there are no plans yet, but we'll revisit it shortly

chsi13 commented 6 years ago

Current version is in Alpha. Maybe I can fork it , try it and contribute on it. Prefer avoid to do it directly with Spring integration JMS.

olegz commented 6 years ago

Pull requests are definitely welcomed. Why do you say you prefer to stay away from Spring Integration JMS?

chsi13 commented 6 years ago

We want to implement a choreography-based event model. But we don't have the possibility to use a broker like rabbitMQ directly (it's enterprise politic ;)). And we found that this project really simplify the writing of these flow. Microservices consumes an event, process it and produce another event for another consumer service. That's our model and spring cloud stream fits great for this. What do you think ?

olegz commented 6 years ago

I am not sure that answers my question. Spring Integration JMS provides most of the code that you would need within the binder. We use Spring Integration AMQP and Spring Integration Kafka in both Rabbit and Kafka binders. Basically code reusability where the use of respective Inbound and Outbound adapters allows for a quick binding between the source destination and the channels identified and bound by Source, Processor and/or Sink. Did you have something else in mind?

chsi13 commented 6 years ago

No I know that spring cloud stream is an abstraction on Spring Integration JMS. I just found really great the simplified model that SCS brings on the development of event-driven microservices architecture. So sorry for badly expressed statement. I just want to say that I prefer develop my microservices with the abstraction of SCS instead do it directly with spring jms. Clear for you ?

olegz commented 6 years ago

Yep, got it. So would be interested in reviewing your contribution.

chsi13 commented 6 years ago

Yes do it soon ;-). Thx for answers.