Support for optional namespaces

[bilus]

Overview

Optional namespacing for aggregate/projection streams and events allowing for isolation between different applications.

As a result, aggregates event listeners will load events generated within the namespace. If no namespace is provided, identical event or aggregate names may result in undefined behavior.

Usage

Akasha::Repository.new(store, namespace: 'myapp.example.com')

Implementation

If a namespace name is provided:

1. Aggregate streams are prefixed with the namespace.
2. Projection stream is prefixed with the namespace.
3. Every event's metadata contains the namespace attribute containing the namespace name.
4. Event listeners ignore events with a different namespace in their metadata.

[hipek]

LGTM

[brapacz]

LGTM, but version in change log is set to xx

[Holek]

I'm not a big fan of Javascript hardcoded in Ruby files. Have you considered using ERB templates?

[bilus]

I'll create an issue about refactoring tasks.