Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@node-ts/bus-messages

Package Overview
Dependencies
Maintainers
1
Versions
31
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@node-ts/bus-messages - npm Package Compare versions

Comparing version 0.3.2 to 1.0.0-alpha.0

8

dist/index.js
"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
const tslib_1 = require("tslib");
tslib_1.__exportStar(require("./message"), exports);
tslib_1.__exportStar(require("./command"), exports);
tslib_1.__exportStar(require("./event"), exports);
tslib_1.__exportStar(require("./message-attributes"), exports);
(0, tslib_1.__exportStar)(require("./message"), exports);
(0, tslib_1.__exportStar)(require("./command"), exports);
(0, tslib_1.__exportStar)(require("./event"), exports);
(0, tslib_1.__exportStar)(require("./message-attributes"), exports);
//# sourceMappingURL=index.js.map
declare type Uuid = string;
export interface MessageAttributeMap {
[key: string]: string | number | undefined;
[key: string]: string | number | boolean | undefined;
}
export declare type Attributes<AttributesType extends MessageAttributeMap> = AttributesType;
export declare type StickyAttributes<StickyAttributesType extends MessageAttributeMap> = StickyAttributesType;
/**

@@ -9,3 +11,3 @@ * Options that control the behaviour around how the message is sent and

*/
export declare class MessageAttributes<AttributeType extends MessageAttributeMap = MessageAttributeMap, StickyAttributeType extends MessageAttributeMap = MessageAttributeMap> {
export interface MessageAttributes<AttributesType extends MessageAttributeMap = MessageAttributeMap, StickyAttributesType extends MessageAttributeMap = MessageAttributeMap> {
/**

@@ -27,3 +29,3 @@ * An identifier that can be used to relate or group messages together.

*/
attributes: AttributeType;
attributes: AttributesType;
/**

@@ -37,9 +39,4 @@ * Additional metadata that will be sent alongside the message payload.

*/
stickyAttributes: StickyAttributeType;
constructor(properties?: {
correlationId?: Uuid;
attributes?: AttributeType;
stickyAttributes?: StickyAttributeType;
});
stickyAttributes: StickyAttributesType;
}
export {};
"use strict";
Object.defineProperty(exports, "__esModule", { value: true });
exports.MessageAttributes = void 0;
/**
* Options that control the behaviour around how the message is sent and
* additional information that travels with it.
*/
class MessageAttributes {
constructor(properties) {
this.attributes = {};
this.stickyAttributes = {};
if (!!properties) {
const { correlationId, attributes, stickyAttributes } = properties;
this.correlationId = correlationId;
this.attributes = attributes || {};
this.stickyAttributes = stickyAttributes || {};
}
}
}
exports.MessageAttributes = MessageAttributes;
//# sourceMappingURL=message-attributes.js.map
{
"name": "@node-ts/bus-messages",
"description": "A core set of message definitions for distributed applications.",
"version": "0.3.2",
"version": "1.0.0-alpha.0",
"license": "MIT",

@@ -12,2 +12,3 @@ "main": "./dist/index.js",

"build": "tsc --project tsconfig.json --declaration",
"build:watch": "yarn run build --incremental --watch --preserveWatchOutput",
"lint": "tslint --project tsconfig.json 'src/**/*.ts'",

@@ -38,3 +39,3 @@ "lint:fix": "yarn lint --fix"

],
"gitHead": "9c29dcef5e9a60c07f1d9716598e6f64bfc024c3"
"gitHead": "265ea7e16c614971d4b01c3642682d6c93feb52f"
}
# @node-ts/bus-messages
[![Known Vulnerabilities](https://snyk.io/test/github/node-ts/bus/badge.svg)](https://snyk.io/test/github/node-ts/bus)
[![CircleCI](https://circleci.com/gh/node-ts/bus/tree/master.svg?style=svg)](https://circleci.com/gh/node-ts/bus/tree/master)[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](https://opensource.org/licenses/MIT)
This package should be consumed wherever your application defines message contracts. Messages are small pieces of data that get passed around between services. They can define an instruction to perform an action, or report that something has just occurred.
`@node-ts/bus-messages` defines two types of messages:
🔥 📒 👉 View our docs at [https://node-ts.gitbook.io/bus/](https://node-ts.gitbook.io/bus/) 👈 📒 🔥
## Command
## Installation
Commands are a type of message that represents an instruction to do work. These can be technical instructions such as `BackupDatabase`, `ScaleOutLoadBalancer`, or modeled after your business domains like `ChargeCreditCard`, `PostMerchandise`.
Install the **@node-ts/bus-messages** package via npm:
Commands should be named as an instruction, using plain english. The above commands are understandable in plain English that they will do some sort of action.
To implement a comamnd, simply extend `Command` and add in the fields that are relevant to it:
```typescript
import { Command } from '@node-ts/bus-messages'
export class ChargeCreditCard extends Command {
/**
* A unique name that identifies the message. This should be done in namespace style syntax,
* ie: organisation/domain/command-name
*/
$name = 'my-app/accounts/charge-credit-card'
/**
* The contract version of this message. This can be incremented if this message changes the
* number of properties etc to maintain backwards compatibility
*/
$version = 1
/**
* Create a charge on a credit card
* @param creditCardId the card to charge
* @param amount the amount, in USD, to charge the card for
*/
constructor (
readonly creditCardId: string,
readonly amount: number
) {
}
}
```
To send a command, just use `bus.send()`, eg:
```typescript
import { Bus } from '@node-ts/bus-core'
async function chargeCreditCard (
bus: Bus,
creditCardId: string,
amount: number
): Promise<void> {
// Prepare the command
const command = new ChargeCreditCard(creditCardId, amount)
// Send it. @node-ts/bus-core will route it to wherever the handler is
await this.bus.send(command)
}
```
A commands are sent to a single service for processing, and generally result in the publication of one or more `Events`
## Event
An event is a message emitted by the system when "something" happens. Again this could be a technical task being completed such as `DatabaseBackedup`, `LoadBalancerScaledOut` or as a result of changes in your business `CreditCardCharged`, `MerchandisePosted`.
Past-tense should be used when naming an event, since it indicates that an operation was performed on your application.
Events are class definitions that extend from `Event`, eg:
```typescript
import { Event } from '@node-ts/bus-messages'
export class CreditCardCharged extends Event {
/**
* A unique name that identifies the message. This should be done in namespace style syntax,
* ie: organisation/domain/event-name
*/
$name = 'my-app/accounts/credit-card-charged'
/**
* The contract version of this message. This can be incremented if this message changes the
* number of properties etc to maintain backwards compatibility
*/
$version = 1
/**
* A credit card was successfully charged
* @param creditCardId the card that was charged
* @param amount the amount, in USD, the card was charged for
*/
constructor (
readonly creditCardId: string,
readonly amount: number
) {
}
}
```
To publish an event, just use `bus.publish()`, eg:
```typescript
import { Bus } from '@node-ts/bus-core'
async function creditCardChaged (
bus: Bus,
creditCardId: string,
amount: number
): Promise<void> {
// Prepare the event
const event = new CreditCardCharged(creditCardId, amount)
// Publish it. @node-ts/bus-core will route the event to all handlers subscribed to it
await this.bus.publish(event)
}
```
## Usage
Modelling your system using messages like the ones above is very powerful. There are no concerns around what handles them or how they're processed - they just represent an intent to change the system (`command`) or that a change in the system has occurred (`event`).
Over time the number of messages in your library will build up to describe the business domain you're modeling. The messages can be easily defined and well documented so that new developers can understand what they do without any technical detail, which encourages a well-documented system in code.
## Message Attributes
Additional metadata can be added to any type of message as attributes alongside the actual message.
When sending via a transport (eg: SQS, RabbitMQ) the message is sent in a message envelope. Commands and Events are serialized into the message body, whilst attributes are added to the message header.
Attributes are designed to hold data that is related to technical concerns of routing the message, or auditing/logging information such as details around the originator.
```sh
npm install @node-ts/bus-messages
```
type Uuid = string
export interface MessageAttributeMap {
[key: string]: string | number | undefined
[key: string]: string | number | boolean | undefined
}
export type Attributes<AttributesType extends MessageAttributeMap> = AttributesType
export type StickyAttributes<StickyAttributesType extends MessageAttributeMap> = StickyAttributesType
/**

@@ -11,5 +14,5 @@ * Options that control the behaviour around how the message is sent and

*/
export class MessageAttributes<
AttributeType extends MessageAttributeMap = MessageAttributeMap,
StickyAttributeType extends MessageAttributeMap = MessageAttributeMap
export interface MessageAttributes<
AttributesType extends MessageAttributeMap = MessageAttributeMap,
StickyAttributesType extends MessageAttributeMap = MessageAttributeMap
> {

@@ -33,3 +36,3 @@ /**

*/
attributes: AttributeType
attributes: AttributesType

@@ -44,20 +47,4 @@ /**

*/
stickyAttributes: StickyAttributeType
stickyAttributes: StickyAttributesType
}
constructor (properties?: {
correlationId?: Uuid,
attributes?: AttributeType,
stickyAttributes?: StickyAttributeType
}) {
this.attributes = {} as AttributeType
this.stickyAttributes = {} as StickyAttributeType
if (!!properties) {
const { correlationId, attributes, stickyAttributes } = properties
this.correlationId = correlationId
this.attributes = attributes || {} as AttributeType
this.stickyAttributes = stickyAttributes || {} as StickyAttributeType
}
}
}

Sorry, the diff of this file is not supported yet

Sorry, the diff of this file is not supported yet

Sorry, the diff of this file is not supported yet

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc