Hi, Indeed, it will be ideal if we could build some reusable messaging components as guava for Java and curator for zookeeper. One of the key points, IMO, is how we define a common/shared component given those products follow different protocols and have different domain models. Identifying the common modules shared by majority of messaging products should, therefore, be a starting point.
The first shared concept that pops out of my mind is message filtering. > 在 2017年6月26日，下午3:41，yukon <[email protected]> 写道： > > Hi guys, > > John opened a thread in general@incubator to seek interested parties for a > messaging components podling. > > I learned that this podling focus on core, reusable messaging components, such > as benchmark, common api specification, wire protocol bridge and so on. > > IMO, it's a great idea, since there are many messaging solutions in ASF or > other places. > > More info please refer to here: > 1. Ongoing discussion on ActiveMQ community, > https://lists.apache.org/thread.html/ff3ffb0408d299724caadbfb6e3c373e74d5d16def9af0c1a8fd8db9@%3Cdev.activemq.apache.org%3E > 2. Ongoing discussion on incubator community, > https://lists.apache.org/thread.html/14bdf3d93c8c6ac3ac7dd9c1d6e6146fd90991581d80e8c6cfaf9540@%3Cgeneral.incubator.apache.org%3E > > So I opened a thread in our rocketmq community, let's discuss at here if > you have any thoughts about this project. > > Regards, > yukon
