Not a Message Queue (but a simple drop-in event queue)
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.

NoMQ build status

NoMQ is short for Not a Message Queue. It is a distributed event queue that is based on Java 8 and Hazelcast. NoMQ requires NO installation, simply add the jar to your project.

So, what exactly is a distributed event queue? Well, events are published somewhere in a cluster (separate JVM:s). They are then dispatched to all event subscribers in the entire cluster, in the same order, everywhere.


  • Java 8.
  • A sane build environment (e.g. Maven or Gradle).


  • durability: events survive reboots
  • late join: new nodes can join later on
  • ordering: events are delivered in the same order on all nodes
  • no additional installation required: simply include the jars and configure NoMQ from within your Java-code.

Getting started

Publishing an event requires a handle to a NoMQ-instance that contains various publishing methods. ``Event```s are simple types that contains:

  • an event type that describes what kind of event you're triggering
  • a payload that is the actual event data.

When subscribing to events you must register a subscriber using the subscribe method.

The code below creates a NoMQ-instance. The way to do it is to use the NoMQBuilder. In the example you can also see the registration of an event subscriber that simply echoes the id of all received events to System.out.

NoMQ noMQ = NoMQBuilder.builder()
    .subscribe(event -> System.out.println( // register subscriber
    .build()  // Create the NoMQ-instance
    .start(); // Then start it

// Publish an event asynchronously
noMQ.publish("myEvent", "Some payload".getBytes());

The payload for an event is always a byte array (byte[]). This may seem like a strict limitation but there is a a reason for this. Since Hazelcast relies heavy on serialization (Hazelcast distributes the objects to several nodes) it exposes various ways of transforming objects to byte arrays. These include standard Java Serialization where you implement, serialization using HazelCast's DataSerializable or Portable etc. We find that these restrictions (Serializable, Portable etc) are something that we don't want in the NoMQ-API. NoMQ-users should be able to publish any type of event and therefore the entire responsibility of serialization/deserialization is in your hands, that's fair, isn't it?

With that being said, in order to publish payloads of any type simply convert the payload to a byte array using a payload converter. The code below uses a converter that converts a payload of type String to a byte[].

    "myEvent",          // Event name
    "Some payload",     // The payload (String)
    String::getBytes);  // Converter

The published byte array is part of the event object that is delivered to the event subscribers. If you want to subscribe to the payload in some other format than a byte array it is possible to provide a reverse payload converter for subscriptions as well.

// Register payload subscriber and converter,
// the byte[] is converted to a String
NoMQ noMQ = NoMQBuilder.builder()
        "myEvent",                      // Event name
        str -> System.out.println(str), // Subscriber
        bytes -> new String(bytes))     // Converter

// Publish using a converter as in the example above
noMQ.publish("myEvent", "A string", str -> str.getBytes());

Handling success and failure

NoMQ is totally non-blocking. This means that whenever you publish an event the publishing is asynchronous. But what if you wanted to know if something failed or find out the details about the event that was (eventually) published? Well, then you simply chain the callback handlers (via a class called PublishResult) as in the example below:

    .onSuccess(event -> System.out.println("Event was published: " +
    .onFailure(thr -> {/* Do something to handle the error. */});

Easy peasy, isn't it?

Late join




Dependecies (Maven)

NoMQ is available as a Maven artefact from TODO:...


Configuring the cluster

NoMQ is based on Hazelcast - to set up a cluster follow the instructions on the Hazelcast website (

Issues and feature requests

NoMQ uses GitHub Issues for feature requests and issue tracking.


Copyright 2014 the original author or authors

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.