npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

nocms-aggregate-root

v1.0.1

Published

Aggregate root for event sourcing in node

Downloads

3

Readme

NoCMS Event Sourcing - Aggregate Root

This is an aggregate root used for event sourcing in node.js. The aggregate root can be configured with a custom event store. It save events raised by commands and iterates over them, returning the final result. An optional custom event bus can also be applied.

Packages for Azure SQL store, Azure Service Bus, and RabbitMQ will eventually be available.

semantic-release Dependency Status devDependencies

Installation

Install using npm: npm i nocms-aggregate-root -S

Usage

Example

const customerAggregateRoot = require('nocms-aggregate-root');
customerAggregateRoot
  .setStore(store)
  .setCommandHandlers(commandHandlers)
  .setEventHandlers(eventHandlers);

await customerAggregateRoot.addCommand(id, 'createCustomer', { name: 'Jørgen', isCreate: true });
const customer = await customerAggregateRoot.load(id); // { name: 'Jørgen', streamRevision: 1, id: '1', dispatched: false }

Visit the example/ folder for a complete, running example.

Creating the store

The aggregate root requires a store for saving events in a stream. The store should be provided, using the setStore function, which takes an object with the following API:

saveEvent(event)

The event object represents an occurence of a certain event in time. The following fields are required:

| Field | Description | |===============|================================================| | aggregateId | Id of the aggregate root, which is used to group all the events | | eventType | Name of the event type, which is used to resolve the event handler | | streamRevision | Revision number of the event stream, used for chronologically ordering the events | | payload | Object for the data of the event. |

getEvents(aggregateId)

Should return an array of all the events of an aggregate identified by aggregateId, ordered by stream revision.

markEventDispatched(aggregateId, streamRevision)

When an event bus is used, in order to make sure that an event is published on the bus, the event is initially flagged as undispatched. After a successful bus.publish is called (automatically invoked by this package), store.markEventDispatched is also automatically invoked.

This function should set dispatched = true on the event identified by aggregateId and streamRevision.

Creating the bus

Commit message format and publishing

This repository is published using semantic-release, with the default AngularJS Commit Message Conventions.