lightweight publish/subscribe framework in java [closed]

Answer 1

JMS is as light or heavy as you configure it. We use for example HornetQ in one project with an in memory queue. It is easy to setup, doesn't need any JNDI based configuration and is really easy to use.

I believe that JMS as an API for Message Pub/Sub is as easy as it gets. (And not easier ;)

Answer 2

I think Camel is also a good candidate. Especially with the publish-subscribe pattern

Camel can be embedded and is lightweight. It proposes Enterprise Integration Patterns - many useful tools for integration, inside an application or even with other actors (hence 'Integration').

It compares to Spring Integration but more complete IMO.

Answer 3

If you are crossing process boundaries then some degree of "weight" is going to be incurred. Why do you say that JMS is heavyweight? The API is quite simple? There are supposedly light-weight implementations, for example link text heavier costs such a persistence and transactionality are optional.

What do you need that is lighter than this?

Answer 4

Bob Lee has a QueueFile class at http://snipt.org/GWm/ that you might find interesting. It's a simple persistent queue and could be used by multiple consumers. It sounds like you don't need persistence, but since the whole thing is so lightweight it could still be useful.

Answer 5

It seems this fits the requirements:

EventBus from Google Guava Library - "Publish-subscribe-style communication between components without requiring the components to explicitly register with one another". It can also be an AsyncEventBus that will dispatch events on another thread.

Some extra options to consider:

1. If it's in same process it's possible the Observer pattern can be used. Subscribers can add listeners and receive event notifications. Observable is already part of the Java API.

2. FFMQ is a full Java, light-weight, Fast JMS 1.1 Queue implementation.

Answer 6

Since you're using Spring, I don't know if you're aware that Spring has its own lightweight event framework. It's used primarily within the framework itself, but it's perfectly usable by application code.

By default, it's synchronous pub/sub, but you can make it asynchronous using an ApplicationEventMulticaster.