Security News
Input Validation Vulnerabilities Dominate MITRE's 2024 CWE Top 25 List
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
cqrs-eventstore
Advanced tools
CQRS and Event Sourcing for Node.js 4+, supporting snapshots, built-in cache, hooks and payload compression
You need Node.js 4+ to use it!
$ npm install cqrs-eventstore
A full example is provided in the demo folder. To run it:
In order to use CQRS-EventStore, you need to implement your own aggregate and DTOs. Your aggregate must extend Aggregate.
An aggregate example including the DTOs:
"use strict";
class BaseEvent {
constructor() {
this.id
this.version
}
}
module.exports = BaseEvent
"use strict"
const BaseEvent = require("./baseEvent")
class AddressUpdated extends BaseEvent {
constructor(address) {
super()
this.address = address
}
}
module.exports = AddressUpdated
"use strict"
const BaseEvent = require("./baseEvent")
class MobileUpdated extends BaseEvent {
constructor(mobile) {
super()
this.mobile = mobile
}
}
module.exports = MobileUpdated
"use strict"
const BaseEvent = require("./baseEvent")
class UserInfoCreated extends BaseEvent {
constructor(name, surname, address, mobile) {
super()
this.name = name
this.surname = surname
this.address = address
this.mobile = mobile
}
}
module.exports = UserInfoCreated
"use strict"
const NodeEventStore = require("cqrs-eventstore")
const UserInfoCreated = require("./dto/userInfoCreated")
const AddressUpdated = require("./dto/addressUpdated")
const MobileUpdated = require("./dto/mobileUpdated")
const clone = require("clone") //Clone is used for the snapshot, it's totally up to you how to implement it.
function UserInfo(id) {
//We are not exposing the UserInfo to the outside world, but we access to it through query.
function UserInfoObj() {
this.name
this.surname
this.address
this.mobile
}
let _userInfo
class UserInfo extends NodeEventStore.Aggregate {
constructor(id) {
super(id)
_userInfo = new UserInfoObj()
}
snapshot() {
return clone(_userInfo)
}
applySnapshot(payload) {
_userInfo = payload
}
//Queries
get Mobile() {
return _userInfo.mobile
}
get Address() {
return _userInfo.address
}
//Mutators
initialize(name, surname, address, mobile) {
super.raiseEvent(new UserInfoCreated(name, surname, address, mobile))
}
updateAddress(address) {
super.raiseEvent(new AddressUpdated(address))
}
updateMobile(mobile, hookFn) {
super.raiseEvent(new MobileUpdated(mobile), hookFn)
}
//Apply
UserInfoCreated(payload) {
_userInfo.name = payload.name
_userInfo.surname = payload.surname
_userInfo.address = payload.address
_userInfo.mobile = payload.mobile
}
AddressUpdated(payload) {
_userInfo.address = payload.address
}
MobileUpdated(payload) {
_userInfo.mobile = payload.mobile
}
}
return new UserInfo(id)
}
module.exports = UserInfo
In order to implement your own persistence layer, you need to extend PersistenceAdapter and register it into the configurator (I'll show it later). The methods save, readSnapshot and readEvents must be implemented. All methods must return a promise. In the save method you need to persist your events and snapshot.
Below an example how to implement a sqlite persistor.
"use strict"
const nodeEventStore = require("cqrs-eventstore")
const fs = require("fs");
const sqlite3 = require("sqlite3").verbose();
const _ = require("underscore")
const util = require("util")
const Guid = require("guid")
class SqlitePersistor extends nodeEventStore.PersistenceAdapter {
constructor() {
super()
const file = "eventStore.db";
const exists = fs.existsSync(file);
this.db = new sqlite3.Database(file);
this.db.serialize(() => {
if (!exists) {
this.db.run("CREATE TABLE Events (id TEXT, streamId TEXT, version INTEGER, timestamp TEXT, eventType TEXT, payload BLOB)");
this.db.run("CREATE TABLE Snapshots (id TEXT, streamId TEXT, version INTEGER, timestamp TEXT, payload BLOB)");
}
});
}
save(events, snapshots) {
const self = this;
return new Promise((resolve, reject) => {
self.db.serialize(() => {
try {
self.db.run("BEGIN TRANSACTION")
_.each(events, (e) => {
self.db.run("INSERT INTO Events VALUES (?, ?, ?, ?, ?, ?)", Guid.raw(), e.streamId, e.version, new Date(), e.eventType, e.payload)
})
_.each(snapshots, (e) => {
self.db.run("INSERT INTO Snapshots VALUES (?, ?, ?, ?, ?)", Guid.raw(), e.streamId, e.version, new Date(), e.payload)
})
self.db.run("COMMIT TRANSACTION")
resolve()
} catch (err) {
self.db.run("ROLLBACK TRANSACTION")
reject(err)
}
})
})
}
//return a promise
readSnapshot(id) {
return new Promise((resolve, reject) => {
this.db.get("SELECT * FROM Snapshots WHERE streamId = ? ORDER BY version DESC LIMIT 1", [id], (err, row) => {
if (err) return reject(err)
resolve(row)
});
})
}
//return a promise
readEvents(id, fromVersion) {
return new Promise((resolve, reject) => {
this.db.all("SELECT * FROM Events WHERE streamId = ? AND version > ? ORDER BY version", [id, fromVersion], (err, rows) => {
if (err) return reject(err)
resolve(rows)
});
})
}
}
module.exports = new SqlitePersistor()
CQRS-EventStore comes with a build-in hook functionality. We can execute a task after each commands.
A simple hook that print into the console on each mobile number update:
"use strict"
const util = require("util")
module.exports = evt => {
console.log(util.format("Mobile number updated %s", evt.mobile))
}
Hooks need to be registered into the configurator
Before to use CQRS-EventStore, we need to configure it.
The parameters are:
"use strict"
const NodeEventStore = require("cqrs-eventstore")
const UserInfoAggregate = require("./userInfoAggregate")
const mobileUpdatedHook = require("./mobile-updated-hook")
//We need to register the hooks here, the name of the hook must match the apply method
NodeEventStore.registerHook("MobileUpdated", mobileUpdatedHook)
//Configuration
const EventStore = NodeEventStore.initialize({
cacheExpiration: 180,
cacheDeleteCheckInterval: 60,
repository: require("./sqlite-persistor"),
snapshotEvery: 5,
zipPayload: true
})
const repository = new EventStore.Repository(UserInfoAggregate)
let userInfoAggregate = new UserInfoAggregate(1)
userInfoAggregate.initialize("Gennaro", "Del Sorbo", "Main Street", "09762847")
repository.save(userInfoAggregate).then(() => {
userInfoAggregate.updateMobile("333");
userInfoAggregate.updateMobile("334");
userInfoAggregate.updateMobile("335");
userInfoAggregate.updateAddress("12, Main St.")
userInfoAggregate.updateAddress("15, Main St.")
repository.save(userInfoAggregate).then(() => {
console.log("all saved")
console.log("try a read")
repository.read(1).then(userInfo => {
console.log(userInfo.Mobile)
console.log(userInfo.Address)
}).catch(e => {
console.log(e)
});
})
}).catch(err => {
console.log(err)
})
FAQs
CQRS and Event Sourcing for Node.js 4+, supporting snapshots, built-in cache, hooks and payload compression
The npm package cqrs-eventstore receives a total of 0 weekly downloads. As such, cqrs-eventstore popularity was classified as not popular.
We found that cqrs-eventstore demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.
Research
Security News
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.