• Stars
    star
    539
  • Rank 82,402 (Top 2 %)
  • Language
    JavaScript
  • License
    MIT License
  • Created about 13 years ago
  • Updated over 2 years ago

Reviews

There are no reviews yet. Be the first to send feedback to the community and the maintainers!

Repository Details

EventStore Implementation in node.js

⚠️ IMPORTANT NEWS! πŸ“°

I’ve been dealing with CQRS, event-sourcing and DDD long enough now that I don’t need working with it anymore unfortunately, so at least for now this my formal farewell!

I want to thank everyone who has contributed in one way or another. Especially...

  • Jan, who introduced me to this topic.
  • Dimitar, one of the last bigger contributors and maintainer.
  • My last employer, who gave me the possibility to use all these CQRS modules in a big Cloud-System.
  • My family and friends, who very often came up short.

Finally, I would like to thank Golo Roden, who was there very early at the beginning of my CQRS/ES/DDD journey and is now here again to take over these modules.

Golo Roden is the founder, CTO and managing director of the native web, a company specializing in native web technologies. Among other things, he also teaches CQRS/ES/DDD etc. and based on his vast knowledge, he brought wolkenkit to life. wolkenkit is a CQRS and event-sourcing framework based on Node.js. It empowers you to build and run scalable distributed web and cloud services that process and store streams of domain events.

With this step, I can focus more on i18next, locize and localistars. I'm happy about that. 😊

So, there is no end, but the start of a new phase for my CQRS modules. πŸ˜‰

I wish you all good luck on your journey.

Who knows, maybe we'll meet again in a github issue or PR at i18next πŸ˜‰

Adriano Raiano


Introduction

JS.ORG travis npm

The project goal is to provide an eventstore implementation for node.js:

  • load and store events via EventStream object
  • event dispatching to your publisher (optional)
  • supported Dbs (inmemory, mongodb, redis, tingodb, elasticsearch, azuretable, dynamodb)
  • snapshot support
  • query your events

Consumers

Installation

npm install eventstore

Usage

Require the module and init the eventstore:

var eventstore = require('eventstore');

var es = eventstore();

By default the eventstore will use an inmemory Storage.

Logging

For logging and debugging you can use debug by TJ Holowaychuk

simply run your process with

DEBUG=eventstore* node app.js

Provide implementation for storage

example with mongodb:

var es = require('eventstore')({
  type: 'mongodb',
  host: 'localhost',                             // optional
  port: 27017,                                   // optional
  dbName: 'eventstore',                          // optional
  eventsCollectionName: 'events',                // optional
  snapshotsCollectionName: 'snapshots',          // optional
  transactionsCollectionName: 'transactions',    // optional
  timeout: 10000,                                // optional
  // emitStoreEvents: true                       // optional, by default no store events are emitted
  // maxSnapshotsCount: 3                        // optional, defaultly will keep all snapshots
  // authSource: 'authedicationDatabase'         // optional
  // username: 'technicalDbUser'                 // optional
  // password: 'secret'                          // optional
  // url: 'mongodb://user:pass@host:port/db?opts // optional
  // positionsCollectionName: 'positions'        // optional, defaultly wont keep position
});

example with redis:

var es = require('eventstore')({
  type: 'redis',
  host: 'localhost',                          // optional
  port: 6379,                                 // optional
  db: 0,                                      // optional
  prefix: 'eventstore',                       // optional
  eventsCollectionName: 'events',             // optional
  snapshotsCollectionName: 'snapshots',       // optional
  timeout: 10000                              // optional
  // emitStoreEvents: true,                   // optional, by default no store events are emitted
  // maxSnapshotsCount: 3                     // optional, defaultly will keep all snapshots
  // password: 'secret'                       // optional
});

example with tingodb:

var es = require('eventstore')({
  type: 'tingodb',
  dbPath: '/path/to/my/db/file',              // optional
  eventsCollectionName: 'events',             // optional
  snapshotsCollectionName: 'snapshots',       // optional
  transactionsCollectionName: 'transactions', // optional
  timeout: 10000,                             // optional
  // emitStoreEvents: true,                   // optional, by default no store events are emitted
  // maxSnapshotsCount: 3                     // optional, defaultly will keep all snapshots
});

example with elasticsearch:

var es = require('eventstore')({
  type: 'elasticsearch',
  host: 'localhost:9200',                     // optional
  indexName: 'eventstore',                    // optional
  eventsTypeName: 'events',                   // optional
  snapshotsTypeName: 'snapshots',             // optional
  log: 'warning',                             // optional
  maxSearchResults: 10000,                    // optional
  // emitStoreEvents: true,                   // optional, by default no store events are emitted
  // maxSnapshotsCount: 3                     // optional, defaultly will keep all snapshots
});

example with custom elasticsearch client (e.g. with AWS ElasticSearch client. Note http-aws-es package usage in this example):

var elasticsearch = require('elasticsearch');

var esClient = = new elasticsearch.Client({
  hosts: 'SOMETHING.es.amazonaws.com',
  connectionClass: require('http-aws-es'),
  amazonES: {
    region: 'us-east-1',
    accessKey: 'REPLACE_AWS_accessKey',
    secretKey: 'REPLACE_AWS_secretKey'
  }
});

var es = require('eventstore')({
  type: 'elasticsearch',
  client: esClient,
  indexName: 'eventstore',
  eventsTypeName: 'events',
  snapshotsTypeName: 'snapshots',
  log: 'warning',
  maxSearchResults: 10000
});

example with azuretable:

var es = require('eventstore')({
  type: 'azuretable',
  storageAccount: 'nodeeventstore',
  storageAccessKey: 'aXJaod96t980AbNwG9Vh6T3ewPQnvMWAn289Wft9RTv+heXQBxLsY3Z4w66CI7NN12+1HUnHM8S3sUbcI5zctg==',
  storageTableHost: 'https://nodeeventstore.table.core.windows.net/',
  eventsTableName: 'events',               // optional
  snapshotsTableName: 'snapshots',         // optional
  timeout: 10000,                          // optional
  emitStoreEvents: true                    // optional, by default no store events are emitted
});

example with dynamodb:

var es = require('eventstore')({
    type: 'dynamodb',
    eventsTableName: 'events',                  // optional
    snapshotsTableName: 'snapshots',            // optional
    undispatchedEventsTableName: 'undispatched' // optional
    EventsReadCapacityUnits: 1,                 // optional
    EventsWriteCapacityUnits: 3,                // optional
    SnapshotReadCapacityUnits: 1,               // optional
    SnapshotWriteCapacityUnits: 3,              // optional
    UndispatchedEventsReadCapacityUnits: 1,     // optional
    UndispatchedEventsReadCapacityUnits: 1,     // optional
    useUndispatchedEventsTable: true            // optional
    eventsTableStreamEnabled: false             // optional
    eventsTableStreamViewType: 'NEW_IMAGE',     // optional
    emitStoreEvents: true                       // optional, by default no store events are emitted
});

DynamoDB credentials are obtained by eventstore either from environment vars or credentials file. For setup see AWS Javascript SDK.

DynamoDB provider supports DynamoDB local for local development via the AWS SDK endpoint option. Just set the $AWS_DYNAMODB_ENDPOINT (or %AWS_DYNAMODB_ENDPOINT% in Windows) environment variable to point to your running instance of Dynamodb local like this:

$ export AWS_DYNAMODB_ENDPOINT=http://localhost:8000

Or on Windows:

> set AWS_DYNAMODB_ENDPOINT=http://localhost:8000

The useUndispatchedEventsTable option to available for those who prefer to use DyanmoDB.Streams to pull events from the store instead of the UndispatchedEvents table. The default is true. Setting this option to false will result in the UndispatchedEvents table not being created at all, the getUndispatchedEvents method will always return an empty array, and the setEventToDispatched will effectively do nothing.

Refer to StreamViewType for a description of the eventsTableStreamViewType option

Built-in event publisher (optional)

if defined the eventstore will try to publish AND set event do dispatched on its own...

sync interface

es.useEventPublisher(function(evt) {
  // bus.emit('event', evt);
});

async interface

es.useEventPublisher(function(evt, callback) {
  // bus.sendAndWaitForAck('event', evt, callback);
});

catch connect and disconnect events

es.on('connect', function() {
  console.log('storage connected');
});

es.on('disconnect', function() {
  console.log('connection to storage is gone');
});

define event mappings [optional]

Define which values should be mapped/copied to the payload event.

es.defineEventMappings({
  id: 'id',
  commitId: 'commitId',
  commitSequence: 'commitSequence',
  commitStamp: 'commitStamp',
  streamRevision: 'streamRevision'
});

initialize

es.init(function (err) {
  // this callback is called when all is ready...
});

// or

es.init(); // callback is optional

working with the eventstore

get the eventhistory (of an aggregate)

es.getEventStream('streamId', function(err, stream) {
  var history = stream.events; // the original event will be in events[i].payload

  // myAggregate.loadFromHistory(history);
});

or

es.getEventStream({
  aggregateId: 'myAggregateId',
  aggregate: 'person',          // optional
  context: 'hr'                 // optional
}, function(err, stream) {
  var history = stream.events; // the original event will be in events[i].payload

  // myAggregate.loadFromHistory(history);
});

'streamId' and 'aggregateId' are the same... In ddd terms aggregate and context are just to be more precise in language. For example you can have a 'person' aggregate in the context 'human ressources' and a 'person' aggregate in the context of 'business contracts'... So you can have 2 complete different aggregate instances of 2 complete different aggregates (but perhaps with same name) in 2 complete different contexts

you can request an eventstream even by limit the query with a 'minimum revision number' and a 'maximum revision number'

var revMin = 5,
    revMax = 8; // if you omit revMax or you define it as -1 it will retrieve until the end

es.getEventStream('streamId' || {/* query */}, revMin, revMax, function(err, stream) {
  var history = stream.events; // the original event will be in events[i].payload

  // myAggregate.loadFromHistory(history);
});

store a new event and commit it to store

es.getEventStream('streamId', function(err, stream) {
  stream.addEvent({ my: 'event' });
  stream.addEvents([{ my: 'event2' }]);

  stream.commit();

  // or

  stream.commit(function(err, stream) {
    console.log(stream.eventsToDispatch); // this is an array containing all added events in this commit.
  });
});

if you defined an event publisher function the committed event will be dispatched to the provided publisher

if you just want to load the last event as stream you can call getLastEventAsStream instead of Β΄getEventStreamΒ΄.

working with snapshotting

get snapshot and eventhistory from the snapshot point

es.getFromSnapshot('streamId', function(err, snapshot, stream) {
  var snap = snapshot.data;
  var history = stream.events; // events history from given snapshot

  // myAggregate.loadSnapshot(snap);
  // myAggregate.loadFromHistory(history);
});

or

es.getFromSnapshot({
  aggregateId: 'myAggregateId',
  aggregate: 'person',          // optional
  context: 'hr'                 // optional
}, function(err, snapshot, stream) {
  var snap = snapshot.data;
  var history = stream.events; // events history from given snapshot

  // myAggregate.loadSnapshot(snap);
  // myAggregate.loadFromHistory(history);
});

you can request a snapshot and an eventstream even by limit the query with a 'maximum revision number'

var revMax = 8; // if you omit revMax or you define it as -1 it will retrieve until the end

es.getFromSnapshot('streamId' || {/* query */}, revMax, function(err, snapshot, stream) {
  var snap = snapshot.data;
  var history = stream.events; // events history from given snapshot

  // myAggregate.loadSnapshot(snap);
  // myAggregate.loadFromHistory(history);
});

create a snapshot point

es.getFromSnapshot('streamId', function(err, snapshot, stream) {

  var snap = snapshot.data;
  var history = stream.events; // events history from given snapshot

  // myAggregate.loadSnapshot(snap);
  // myAggregate.loadFromHistory(history);

  // create a new snapshot depending on your rules
  if (history.length > myLimit) {
    es.createSnapshot({
      streamId: 'streamId',
      data: myAggregate.getSnap(),
      revision: stream.lastRevision,
      version: 1 // optional
    }, function(err) {
      // snapshot saved
    });

    // or

    es.createSnapshot({
      aggregateId: 'myAggregateId',
      aggregate: 'person',          // optional
      context: 'hr'                 // optional
      data: myAggregate.getSnap(),
      revision: stream.lastRevision,
      version: 1 // optional
    }, function(err) {
      // snapshot saved
    });
  }

  // go on: store new event and commit it
  // stream.addEvents...

});

You can automatically clean older snapshots by configuring the number of snapshots to keep with maxSnapshotsCount in eventstore options.

own event dispatching (no event publisher function defined)

es.getUndispatchedEvents(function(err, evts) {
  // or es.getUndispatchedEvents('streamId', function(err, evts) {
  // or es.getUndispatchedEvents({ // free choice (all, only context, only aggregate, only aggregateId...)
  //                                context: 'hr',
  //                                aggregate: 'person',
  //                                aggregateId: 'uuid'
  //                              }, function(err, evts) {

  // all undispatched events
  console.log(evts);

  // dispatch it and set the event as dispatched

  for (var e in evts) {
    var evt = evts[r];
    es.setEventToDispatched(evt, function(err) {});
    // or
    es.setEventToDispatched(evt.id, function(err) {});
  }

});

query your events

for replaying your events or for rebuilding a viewmodel or just for fun...

skip, limit always optional

var skip = 0,
    limit = 100; // if you omit limit or you define it as -1 it will retrieve until the end

es.getEvents(skip, limit, function(err, evts) {
  // if (events.length === amount) {
  //   events.next(function (err, nextEvts) {}); // just call next to retrieve the next page...
  // } else {
  //   // finished...
  // }
});

// or

es.getEvents('streamId', skip, limit, function(err, evts) {
  // if (events.length === amount) {
  //   events.next(function (err, nextEvts) {}); // just call next to retrieve the next page...
  // } else {
  //   // finished...
  // }
});

// or

es.getEvents({ // free choice (all, only context, only aggregate, only aggregateId...)
  context: 'hr',
  aggregate: 'person',
  aggregateId: 'uuid'
}, skip, limit, function(err, evts) {
  // if (events.length === amount) {
  //   events.next(function (err, nextEvts) {}); // just call next to retrieve the next page...
  // } else {
  //   // finished...
  // }
});

by revision

revMin, revMax always optional

var revMin = 5,
    revMax = 8; // if you omit revMax or you define it as -1 it will retrieve until the end

es.getEventsByRevision('streamId', revMin, revMax, function(err, evts) {});

// or

es.getEventsByRevision({
  aggregateId: 'myAggregateId',
  aggregate: 'person',          // optional
  context: 'hr'                 // optional
}, revMin, revMax, function(err, evts) {});

by commitStamp

skip, limit always optional

var skip = 0,
    limit = 100; // if you omit limit or you define it as -1 it will retrieve until the end

es.getEventsSince(new Date(2015, 5, 23), skip, limit, function(err, evts) {
  // if (events.length === amount) {
  //   events.next(function (err, nextEvts) {}); // just call next to retrieve the next page...
  // } else {
  //   // finished...
  // }
});

// or

es.getEventsSince(new Date(2015, 5, 23), limit, function(err, evts) {
  // if (events.length === amount) {
  //   events.next(function (err, nextEvts) {}); // just call next to retrieve the next page...
  // } else {
  //   // finished...
  // }
});

// or

es.getEventsSince(new Date(2015, 5, 23), function(err, evts) {
  // if (events.length === amount) {
  //   events.next(function (err, nextEvts) {}); // just call next to retrieve the next page...
  // } else {
  //   // finished...
  // }
});

streaming your events

Some databases support streaming your events, the api is similar to the query one

skip, limit always optional

var skip = 0,
    limit = 100; // if you omit limit or you define it as -1 it will retrieve until the end

var stream = es.streamEvents(skip, limit);
// or
var stream = es.streamEvents('streamId', skip, limit);
// or by commitstamp
var stream = es.streamEventsSince(new Date(2015, 5, 23), skip, limit);
// or by revision
var stream = es.streamEventsByRevision({
  aggregateId: 'myAggregateId',
  aggregate: 'person',
  context: 'hr',
});

stream.on('data', function(e) {
  doSomethingWithEvent(e);
});

stream.on('end', function() {
  console.log('no more evets');
});

// or even better
stream.pipe(myWritableStream);

currently supported by:

  1. mongodb

get the last event

for example to obtain the last revision nr

es.getLastEvent('streamId', function(err, evt) {
});

// or

es.getLastEvent({ // free choice (all, only context, only aggregate, only aggregateId...)
  context: 'hr',
  aggregate: 'person',
  aggregateId: 'uuid'
} function(err, evt) {
});

obtain a new id

es.getNewId(function(err, newId) {
  if(err) {
    console.log('ohhh :-(');
    return;
  }

  console.log('the new id is: ' + newId);
});

position of event in store

some db implementations support writing the position of the event in the whole store additional to the streamRevision.

currently those implementations support this:

  1. inmemory ( by setting ```trackPosition`` option )
  2. mongodb ( by setting positionsCollectionName option)

special scaling handling with mongodb

Inserting multiple events (documents) in mongodb, is not atomic. For the eventstore tries to repair itself when calling getEventsByRevision. But if you want you can trigger this from outside:

es.store.getPendingTransactions(function(err, txs) {
  if(err) {
    console.log('ohhh :-(');
    return;
  }

  // txs is an array of objects like:
  // {
  //   _id: '/* the commitId of the committed event stream */',
  //   events: [ /* all events of the committed event stream */ ],
  //   aggregateId: 'aggregateId',
  //   aggregate: 'aggregate', // optional
  //   context: 'context'      // optional
  // }

  es.store.getLastEvent({
    aggregateId: txs[0].aggregateId,
    aggregate: txs[0].aggregate, // optional
    context: txs[0].context      // optional
  }, function (err, lastEvent) {
    if(err) {
      console.log('ohhh :-(');
      return;
    }

    es.store.repairFailedTransaction(lastEvent, function (err) {
      if(err) {
        console.log('ohhh :-(');
        return;
      }

      console.log('everything is fine');
    });
  });
});

Catch before and after eventstore events

Optionally the eventstore can emit brefore and after events, to enable this feature set the emitStoreEvents to true.

var eventstore = require('eventstore');
var es = eventstore({
  emitStoreEvents: true,
});

es.on('before-clear', function({milliseconds}) {});
es.on('after-clear', function({milliseconds}) {});

es.on('before-get-next-positions', function({milliseconds, arguments: [positions]}) {});
es.on('after-get-next-positions', function({milliseconds, arguments: [positions]}) {});

es.on('before-add-events', function({milliseconds, arguments: [events]}) {});
es.on('after-add-events', function(milliseconds, arguments: [events]) {});

es.on('before-get-events', function({milliseconds, arguments: [query, skip, limit]}) {});
es.on('after-get-events', function({milliseconds, arguments: [query, skip, limit]}) {});

es.on('before-get-events-since', function({milliseconds, arguments: [milliseconds, date, skip, limit]}) {});
es.on('after-get-events-since', function({milliseconds, arguments: [date, skip, limit]}) {});

es.on('before-get-events-by-revision', function({milliseconds, arguments: [query, revMin, revMax]}) {});
es.on('after-get-events-by-revision', function({milliseconds, arguments, [query, revMin, revMax]}) {});

es.on('before-get-last-event', function({milliseconds, arguments: [query]}) {});
es.on('after-get-last-event', function({milliseconds, arguments: [query]}) {});

es.on('before-get-undispatched-events', function({milliseconds, arguments: [query]}) {});
es.on('after-get-undispatched-events', function({milliseconds, arguments: [query]}) {});

es.on('before-set-event-to-dispatched', function({milliseconds, arguments: [id]}) {});
es.on('after-set-event-to-dispatched', function({milliseconds, arguments: [id]}) {});

es.on('before-add-snapshot', function({milliseconds, arguments: [snap]}) {});
es.on('after-add-snapshot', function({milliseconds, arguments: [snap]}) {});

es.on('before-clean-snapshots', function({milliseconds, arguments: [query]}) {});
es.on('after-clean-snapshots', function({milliseconds, arguments: [query]}) {});

es.on('before-get-snapshot', function({milliseconds, arguments: [query, revMax]}) {});
es.on('after-get-snapshot', function({milliseconds, arguments: [query, revMax]}) {});

es.on('before-remove-transactions', function({milliseconds}, arguments: [event]) {});
es.on('after-remove-transactions', function({milliseconds}, arguments: [event]) {});

es.on('before-get-pending-transactions', function({milliseconds}) {});
es.on('after-get-pending-transactions', function({milliseconds}) {});

es.on('before-repair-failed-transactions', function({milliseconds, arguments: [lastEvt]}) {});
es.on('after-repair-failed-transactions', function({milliseconds, arguments: [lastEvt]}) {});

es.on('before-remove-tables', function({milliseconds}) {});
es.on('after-remove-tables', function({milliseconds}) {});

es.on('before-stream-events', function({milliseconds, arguments: [query, skip, limit]}) {});
es.on('after-stream-events', function({milliseconds, arguments: [query, skip, limit]}) {});

es.on('before-stream-events-since', function({milliseconds, arguments: [date, skip, limit]}) {});
es.on('after-stream-events-since', function({milliseconds, arguments: [date, skip, limit]}) {});

es.on('before-get-event-stream', function({milliseconds, arguments: [query, revMin, revMax]}) {});
es.on('after-get-event-stream', function({milliseconds, arguments: [query, revMin, revMax]}) {});

es.on('before-get-from-snapshot', function({milliseconds, arguments: [query, revMax]}) {});
es.on('after-get-from-snapshot', function({milliseconds, arguments: [query, revMax]}) {});

es.on('before-create-snapshot', function({milliseconds, arguments: [obj]}) {});
es.on('after-create-snapshot', function({milliseconds, arguments: [obj]}) {});

es.on('before-commit', function({milliseconds, arguments: [eventstream]}) {});
es.on('after-commit', function({milliseconds, arguments: [eventstream]}) {});

es.on('before-get-last-event-as-stream', function({milliseconds, arguments: [query]}) {});
es.on('after-get-last-event-as-stream', function({milliseconds, arguments: [query]}) {});

Sample Integration

  • nodeCQRS A CQRS sample integrating eventstore

Inspiration

Release notes

Database Support

Currently these databases are supported:

  1. inmemory
  2. mongodb (node-mongodb-native)
  3. redis (redis)
  4. tingodb (tingodb)
  5. azuretable (azure-storage)
  6. dynamodb (aws-sdk)

own db implementation

You can use your own db implementation by extending this...

var Store = require('eventstore').Store,
    util = require('util'),
    _ = require('lodash');

function MyDB(options) {
  options = options || {};
  Store.call(this, options);
}

util.inherits(MyDB, Store);

_.extend(MyDB.prototype, {

  // ...

});

module.exports = MyDB;

and you can use it in this way

var es = require('eventstore')({
  type: MyDB
});
// es.init...

License

Copyright (c) 2018 Adriano Raiano, Jan Muehlemann

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

More Repositories

1

wolkenkit

wolkenkit is an open-source CQRS and event-sourcing framework based on Node.js, and it supports JavaScript and TypeScript.
TypeScript
1,073
star
2

node-cqrs-domain

Node-cqrs-domain is a node.js module based on nodeEventStore that. It can be very useful as domain component if you work with (d)ddd, cqrs, eventdenormalizer, host, etc.
JavaScript
269
star
3

wolkenkit-boards

wolkenkit-boards is a team collaboration application.
JavaScript
245
star
4

uuidv4

uuidv4 creates v4 UUIDs.
TypeScript
177
star
5

cqrs-sample

CQRS, EventSourcing, (DDDD) Sample in node.js
JavaScript
148
star
6

forcedomain

forcedomain is a middleware for Connect and Express that redirects any request to a default domain.
TypeScript
86
star
7

p2p

p2p implements a peer-to-peer protocol.
JavaScript
80
star
8

wolkenkit-eventstore

wolkenkit-eventstore is an open-source eventstore for Node.js that is used by wolkenkit.
JavaScript
79
star
9

roboter

roboter streamlines software development by automating tasks and enforcing conventions.
TypeScript
64
star
10

node-cqrs-saga

Node-cqrs-saga is a node.js module that helps to implement the sagas in cqrs. It can be very useful as domain component if you work with (d)ddd, cqrs, eventdenormalizer, host, etc.
JavaScript
61
star
11

get-next-version

get-next-version gets the next version for your repository according to semantic versioning based on conventional commits.
Go
45
star
12

flaschenpost

flaschenpost is a logger for cloud-based applications.
TypeScript
38
star
13

node-cqrs-eventdenormalizer

Node-cqrs-eventdenormalizer is a node.js module that implements the cqrs pattern. It can be very useful as eventdenormalizer component if you work with (d)ddd, cqrs, domain, host, etc.
JavaScript
38
star
14

boolean

boolean converts lots of things to boolean.
TypeScript
37
star
15

eslint-config-es

eslint-config-es contains a strict ESLint configuration for ES2015+ and TypeScript.
TypeScript
28
star
16

buntstift

buntstift makes the CLI colorful.
TypeScript
27
star
17

node-viewmodel

Node-viewmodel is a node.js module for multiple databases. It can be very useful if you work with (d)ddd, cqrs, eventdenormalizer, host, etc.
JavaScript
27
star
18

crypto2

crypto2 is a convenience wrapper around Node.js' crypto module.
JavaScript
25
star
19

vagrant-node

vagrant-node is the virtual machine used for Node.js development.
Shell
24
star
20

assertthat

assertthat provides fluent TDD.
TypeScript
24
star
21

techlounge-react

techlounge-react contains the samples for the free tech:lounge video course on React.
TypeScript
23
star
22

get-routes

get-routes gets all routes from an Express application.
TypeScript
22
star
23

get-graphql-from-jsonschema

get-graphql-from-jsonschema gets a GraphQL schema from a JSON schema.
TypeScript
22
star
24

tailwind

tailwind is a base module for streaming and evented CQS applications.
JavaScript
20
star
25

cases

cases provides parameterized unit tests for Mocha.
JavaScript
19
star
26

defekt

defekt is custom errors made simple.
TypeScript
19
star
27

tutum

tutum is a wrapper around Tutum's API for Node.js.
JavaScript
19
star
28

comparejs

comparejs implements JavaScript's comparison operators the way you would expect them to be.
TypeScript
18
star
29

commands-events

commands-events provides commands and events for DDD-based applications.
JavaScript
18
star
30

techlounge-docker

techlounge-docker contains the samples for the free tech:lounge video course on Docker.
JavaScript
17
star
31

wolkenkit-todomvc

wolkenkit-todomvc is a todo application.
JavaScript
16
star
32

node-evented-command

provides simple command/event handling for evented systems like cqrs
JavaScript
15
star
33

crew

crew makes managing Docker a breeze.
JavaScript
12
star
34

wolkenkit-nevercompletedgame

wolkenkit-nevercompletedgame is a wolkenkit implementation of nevercompletedgame.com.
JavaScript
11
star
35

json-lines

json-lines streams JSON Lines.
JavaScript
11
star
36

ensurethat

ensurethat validates function arguments.
JavaScript
10
star
37

wolkenkit-react

Official React bindings for wolkenkit.
JavaScript
9
star
38

cqrs

documentation for cqrs modules and libraries
JavaScript
9
star
39

thenativeweb-ux

thenativeweb-ux provides UI components for the native web applications.
TypeScript
9
star
40

runfork

runfork runs a Node.js script isolated as a process.
TypeScript
8
star
41

processenv

processenv parses environment variables.
TypeScript
8
star
42

isolated

isolated provides one-time folders for unit tests.
TypeScript
8
star
43

terminal-img

terminal-img renders an image to the terminal.
TypeScript
8
star
44

json-lines-client

json-lines-client makes parsing JSON lines streams a breeze.
JavaScript
7
star
45

bereich

bereich creates ranges of numbers.
JavaScript
7
star
46

timer2

timer2 is an evented timer.
JavaScript
7
star
47

validate-value

validate-value validates values against JSON schemas.
TypeScript
7
star
48

command-line-interface

command-line-interface is a foundation for CLI applications.
TypeScript
7
star
49

aira

aira runs loops on Roland AIRA series synthesizers.
TypeScript
7
star
50

knockat

knockat waits until a host is reachable.
TypeScript
6
star
51

measure-time

measure-time is a stopwatch.
TypeScript
6
star
52

tourism

tourism is a convenience wrapper for Grunt.
JavaScript
6
star
53

wolkenkit-documentation

wolkenkit-documentation provides the documentation for wolkenkit application developers.
JavaScript
6
star
54

wolkenkit-client-js

wolkenkit-client is a client to access wolkenkit applications.
JavaScript
5
star
55

partof

partof verifies whether one object is part of an other.
TypeScript
5
star
56

formats

formats is a collection of validators.
JavaScript
5
star
57

wolkenkit-core

wolkenkit-core is the domain server of wolkenkit.
JavaScript
5
star
58

nodeenv

nodeenv enables tests to control Node.js environment variables.
TypeScript
5
star
59

datasette

datasette is a key-value container for arbitrary data.
JavaScript
5
star
60

wolkenkit-vm

wolkenkit-vm is a Packer script to setup virtual machines that run wolkenkit.
Shell
5
star
61

findsuggestions

findsuggestions searches haystacks for needles and nails.
JavaScript
4
star
62

try-catch-expression

try-catch-expression provides try..catch as expression.
TypeScript
4
star
63

rdrct

rdrct is a URL shortener and redirection service.
TypeScript
4
star
64

reqd

reqd searches repositories for dependencies.
JavaScript
4
star
65

typedescriptor

typedescriptor identifies and describes types.
TypeScript
4
star
66

limes

limes authenticates users.
TypeScript
4
star
67

wolkenkit-chat-auth0

wolkenkit-chat-auth0 is a chat using wolkenkit and Auth0.
JavaScript
4
star
68

draht

draht provides process-level messaging.
JavaScript
4
star
69

walk-file-tree

walk-file-tree recursively fetches paths to files and directories.
TypeScript
3
star
70

sortby

sortby orders JavaScript arrays using a MongoDB-like syntax.
JavaScript
3
star
71

forany

forany runs a command on every directory.
JavaScript
3
star
72

dotfile-json

dotfile-json reads and writes dot files.
JavaScript
3
star
73

wolkenkit-vagrant

wolkenkit-vagrant provides a Vagrantfile to setup wolkenkit VMs.
3
star
74

flat-object-keys

flat-object-keys returns the flattened keys from an object.
JavaScript
3
star
75

zwitscher

zwitscher is a Twitter CLI.
JavaScript
3
star
76

datendepot

datendepot is a blob storage middleware.
JavaScript
3
star
77

wolkenkit-template-chat

wolkenkit-template-chat is an application template for wolkenkit.
JavaScript
3
star
78

record-stdstreams

record-stdstreams captures process.stdout and process.stderr.
TypeScript
3
star
79

marble-run

marble-run parallelizes asynchronous tasks while keeping some of them in order.
JavaScript
3
star
80

wait-for-signals

wait-for-signals waits for a number of signals before resolving a promise.
TypeScript
3
star
81

whatif

whatif discovers dependencies that need to be updated after updating a package.
JavaScript
3
star
82

update-node

update-node is a script to update repositories to a new Node.js version.
JavaScript
3
star
83

roboter-cli

roboter-cli is the CLI for roboter.
JavaScript
3
star
84

https-or-http

https-or-http runs an HTTPS server or, if not possible, an HTTP server.
JavaScript
2
star
85

deep-hash

deep-hash calculates nested hashes.
JavaScript
2
star
86

get-certificate

get-certificate loads a certificate and its private key from a directory.
JavaScript
2
star
87

shaker

shaker hashes and verifies passwords in a cryptographically secure way using PBKDF2.
JavaScript
2
star
88

streamtoarray

streamtoarray converts a stream to an array.
TypeScript
2
star
89

adventsspecial2021

adventsspecial2021 contains templates, code & co. for the advent special 2021.
JavaScript
2
star
90

isansi

isansi checks whether a string uses ANSI color and style.
TypeScript
2
star
91

temp--performance-workshop

JavaScript
2
star
92

temp--livestream-monitoring

Go
2
star
93

hase

hase handles exchanges and queues on RabbitMQ.
JavaScript
2
star
94

semantic-release-configuration

semantic-release-configuration contains the semantic-release configuration for the native web.
JavaScript
2
star
95

wolkenkit-broker

wolkenkit-broker is the public API server of wolkenkit.
JavaScript
2
star
96

tlse2021-fullstack-testen

tech:lounge Summer Edition 2021 // Fullstack-Testen – von der Unit bis zur UI
TypeScript
2
star
97

wolkenkit-depot

wolkenkit-depot is a service for storing large files.
JavaScript
2
star
98

wolkenkit-console

wolkenkit-console lets you execute domain code from within your browser.
JavaScript
2
star
99

is-subset-of

is-subset-of verifies whether an array or an object is a subset.
TypeScript
2
star
100

is-typescript

is-typescript checks whether a package is built using TypeScript.
TypeScript
1
star