search

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

Other
34 stars 56 forks source link

Updated the project to support the upcoming Fishtown release #36

Open TYsewyn opened 6 years ago

sabbyanandan commented 6 years ago

Hi, @TYsewyn. Thank you for the contribution!

As you'd have noticed, this project has been in a dormant status for a while now. The primary reason being the proprietary nature of some of the binder implementations (eg: IBM MQ) and the fact that some of them don't entirely support the SCSt concepts such as partitioning. Given these limitations, we didn't want to have them officially be part of the release train.

That said, Solace R&D is actively working on a new implementation and likewise, we have some interest from others re: ActiveMQ. The goal is to have those binders hosted in the contributor's GitHub Org/Repos, so they can maintain and release them on demand quickly. We will most likely EOL this repository in the future.

@olegz might have other thoughts to share, too, so let's hear from him.

TYsewyn commented 6 years ago

Thanks for your feedback @sabbyanandan.

Although I know that some binder implementations don't support certain SCSt features like you said, I think this could be a nice tool to create new or adapt existing applications that need to connect to legacy systems, with or without the use of other brokers like RabbitMQ or Kafka. In light of digital transformations, this will also be of great help during the migration of said legacy systems. Therefor I really hope that they will host an implementation in their own GitHub org.

cforce commented 6 years ago

https://github.com/spring-cloud/spring-cloud-stream-binder-solace

Tim Ysewyn notifications@github.com schrieb am Di., 4. Sep. 2018, 21:07:

Thanks for your feedback @sabbyanandan https://github.com/sabbyanandan.

Although I know that some binder implementations don't support certain SCSt features like you said, I really think this could be a nice tool to create new or adapt existing applications that need to connect to legacy systems, with or without the use of other brokers like RabbitMQ or Kafka. In light of digital transformations, this will also be of great help during the migration of said legacy systems. Therefor I really hope that they will host an implementation in their own GitHub org.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/spring-cloud/spring-cloud-stream-binder-jms/pull/36#issuecomment-418482978, or mute the thread https://github.com/notifications/unsubscribe-auth/AAYARqFrMhVe6zzzcl4-ACm-ZCSeoP-Uks5uXs-CgaJpZM4WSBwW .

olegz commented 6 years ago

@TYsewyn I just wanted to add to what Sabby said. We will always work with and help whoever (the contributor) is doing the work to ensure that these binders are following the best practices and idioms of Spring. We already have great experiences of doing exactly that with other vendors.