Muon stack defining an API for persisted event streams. Useful for implementing event sourcing, CQRS, eventually consistent systems
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


Master Build

NPM Stable





Event Persistence Muon Stack

What is a Muon Stack?

Muon is a set of libraries and services that let you build highly effective distributed systems that are message and event oriented.

Muon is structured as a set of libraries, known as muon-core that give a set of infrastructure for building messaging systems. These are available in multiple languages and handle the concerns of discovery, transport, encoding and managing failures. On top of these, the exact messaging semantics that you want to express are built. These are built as a "stack", a set of channels, agents and finally a user facing API that you will use in your application code.

Muon has several such stacks, covering different scenarios and tasks, letting you communicate in various ways, highly distributed, cross platform and taking advantage of best of breed infrastructure and technologies.

What is Event Persistence?

Event Driven Architectures (EDA) are a way for systems and components to interact based on the things that have happened to them, the events about them. Common problems with EDA are that :

  • events can go missing when network transported

  • events can be missed if a component is offline

  • the history is often useful for stream processing analysis, trend detection and the like.

Persisting your events into an event store that permits events so be replayed on demand solves these issues. It allows your applications to emit events, observe them and then selectively replay the streams that you are interested in at some later point as well.

This stack implements an event streaming API client. You can use it to interact with a remote event store, emit events and replay streams on demand.

The server side is implemented by Photon (A Clojure based Event Store with functional event Projections), PhotonLite (an event stream API layer) or any other service (local or remote) that implements the server side of this protocol. This gives you the ability to vary the implementation of your event store, including having different event stores for different streams.

Using this stack

First, you need to start up one of the event stores. If you have used the Muon Starter then you have this running already.


To use the stack in Java, first import Muon, a transport/ discovery and the Event Stack


repositories {
   maven { url '' }
   maven { url '' }

dependencies {
   compile "io.muoncore:muon-core:<version>"
   compile "io.muoncore:muon-transport-amqp:<version>"
   compile "io.muoncore:muon-discovery-amqp:<version>"
   compile "io.muoncore.protocol:stack-event:<version>"

Create an Event Client

This stack allows you to emit events and replay them. For replay, it exposes an API that uses Reactive Streams Publisher/ Subscribers to manage the subscription.

First then, you need to be able to obtain a Subscriber. If you don’t have one already, use a FRP system of some kind to make one. Consider using Spring Reactor, Akka Streams or RxJava, amongst others.

Muon muon = .. create a muon ..;

DefaultEventClient events = new DefaultEventClient(muon);

                .payload(new UserRegistered("Roger", "Rabbit"))

Subscriber<Event> subscriber = .. your subscriber ..

Map<String, Object> args = ...

available args:-

* from - the event order-id to replay from



You can use these to selectively replay certain streams, play them back


To use the client event stack, import Muon, disco/ transport and the stack. This requires the reactive streams stack to be present.

npm install --save muon-core@next
npm install --save muon-amqp@next  #or, any other transport+discovery here
npm install --save muon-stack-reactive-streams@next
npm install --save muon-stack-event@next

Then, create a Muon instance and attach the Event client stack


var Muon = require("muon-core")

var muonurl = process.env.MUON_URL || "amqp://muon:microservices@localhost"

var muon = Muon.create("hello-world-node", muonurl);           (1)

require("muon-stack-event").create(muon)                       (2)

var args = {
  from: <an-order-id>,
  stream-type: cold | hot | hot-cold,

muon.emit({                                                   (3)
        "event-type": "UserRegistered",
        "stream-name": "users",
        "service-id": "my-service",
        payload: {
          firstname: "John",
          lastname: "Simples"
    }).then(function (resp) {"Slack message persisted")

muon.replay("user",{},                                         (4)
   function(data) {
       // on data received
   function(error) {
       // on error
   function() {
       // on complete
  1. Create a new Muon instance, connecting to a local AMQP broker for discovery and transport

  2. Add the event stack, in addition to the reactive streams stack.

  3. Use the added emit method to persist events

  4. Use the added replay method to replay historical events and continue to listen to new events

Getting involved/ adding to this stack.

Additions and extensions to this stack are very welcome.

Particularly of interest are :-

  • Added language support

  • Integrate with javascript FRP libraries.


All code is Copyright (c) Muon Core Ltd 2017.

Muon is Free Software, licensed under the terms of the LGPLv3 license as included in LICENSE

Muon has a commercial-friendly license allowing private forks and closed modifications of all projects, alongside enterprise support and extended support for enterprise technologies and patterns.

This will enable you to use Muon in any situation where your legal team will not accept a Free Software license.

Please see for more detail. You can find the commercial license terms in COMM-LICENSE