[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [messaging-dev] An Attempt at Triaging Issues
|
If we dropped some of the semantic requirements on the API specification and make it being a pure API things would be a lot better.
Let’s talk during the week. I’m typing this totally relaxed from a holiday at the beach. At least it makes a good conversation to have later on :)
Ondro would be the one to arrange it probably. I would agree I don’t think achieving Kafka interoperability is as hard as some people andar w I think it is at least worth discussing. At worst it would mean deprecating some old functionality and/or maybe creating a new profile.
I think the key would be to get IBM and Oracle on board with the idea. I would reach out to Dmitry and Emily to connect with the people working on their Messaging products. At this point I don’t think anyone from those companies is tuned in here.
Reza Rahman
Jakarta EE Ambassador, Author, Blogger, Speaker
Please note views expressed here are my own as an individual community member and do not reflect the views of my employer.
I typed this on the iPhone. Sorry if it sounded weird.
TL;DR can we have a call about the big items ?
It would be nice to have a video call shout the big items.
Tô me the big item is ordering constraints.
When I developed a new messaging system with a few other guys years ago the big problem we had to solve was respecting some ordering constraints from JMS. That imposed a lot of constraints on the data structures used and how to deal with redeliveries.
kafka choose to not be JMs probably because of this. And we could perhaps talk about what we could do about this ?
A video call would be great.
Ondro/others,
As I had suggested, I took a stab at triaging the old issues that have
been there for some time now. Here are the results:
*
https://docs.google.com/spreadsheets/d/1q7XfC-zNend0aT8PKbcOTbKx_9tXPrhmolBI9iPr4BE/edit?usp=sharing
From my perspective here is a summary:
* There are a very small number of issues I think makes sense to look at
for the next release (they are under the label "Worth looking at first").
* There are a very small number of issues folks that end users could
easily pick up (they are under the label "Good first issue").
* The big ticket issues really worth working on are CDI Message
Listeners, a Java SE bootstrap API, AMQP interoperability and Kafka
interoperability/modernizing Messaging. Similarly there are very forward
looking things that are a bit too premature like Reactive Messaging.
* There are a ton of issues I think could be looked at further if there
is time (they are under the label "Should be evaluated further"). I did
order these somewhat, with more end-user focused features first. The
rest I think are mostly issues that vendors would really care about.
These perhaps made sense at a point where there was more time, resources
and investment around this particular specification. I don't think that
is the case for a majority of Messaging vendors any more.
* There are a ton of issues I think should just be closed or assigned
very low priority. They perhaps made sense at a point where there was
more time, resources and investment around this particular
specification. I don't think that is the case for a majority of
Messaging vendors any more.
I do encourage other folks to give this a try - especially the end users
with a genuine real world interest in the specification.
Hope this helps.
Reza Rahman
Jakarta EE Ambassador, Author, Blogger, Speaker
Please note views expressed here are my own as an individual community
member and do not reflect the views of my employer.
_______________________________________________
messaging-dev mailing list
messaging-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org
messaging-dev mailing list
messaging-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org
