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

@ibm_wse/txrouter

v0.1.3

Published

Event based transaction handler working with RabbitMQ

Downloads

3

Readme

TxRouter-SDK for Node.js

Event based distributed transaction solution with RabbitMQ

Introduction

TxRouter is a module which allow you pass domain events between multiple services based on RabbitMQ. Before you install this module, please make sure your RabbitMQ has been initialized by txctl.

Usage as Cli

If you have the admin permission on RabbitMQ, you can use the CLI mode to init the environment. But firstly, you need to init your local configuration to connect RabbitMQ.

Install

> npm install -g txrouter

You can find the help document by below command:

> txctl -h       
Usage: txctl [options] [command]

Options:
  -V, --version     output the version number
  -h, --help        display help for command

Commands:
  config [options]  config the txctl environment
  init              init txrouter in rabbitmq
  get <kind>        get resource list, applications | subscriptions
  apply [options]   apply configuration
  delete [options]  delete resources
  help [command]    display help for command

Step 1: init configuration to access RabbitMQ

# init configuration
> txctl config -i
? ---configuration already existed, do you want to replace it (/Users/sunxiaoyu/.txrouter)?: Yes
? environment name: default
? Choose the protocol: http
? host: localhost
? port: 15672
? cluster: rabbit@e2223bb9f86c
? username: guest
? password: *****
Done!

Step 2: use the environment in configuration:

> txctl config -u default
Done!

Step 3: init RabbitMQ by cli

> txctl init
TxRouter init done!

Step 4: prepare resource definition files

Now you have already created the basic structure in RabbitMQ. Next you need to prepare the YAML files which defined applications and subscriptions.

The application definition YAML looks like below:

apiVersion: 0.0.1
kind: application
name: app01
description: "this is an application"
events:
    - ACTION_CREATE_NEW
    - ACTION_CREATE_SUCCESS
    - ACTION_CREATE_FALSE

The subscription definition YAML looks like:

apiVersion: 0.0.1
kind: subscription
name: app01
description: "this is a desc"
subscriptions:
  - from: provider_01
    events:
      - ORDER_CREATE_SUCCESS
      - ORDER_CREATE_FAILED
  - from: provider_02
    events:
      - ORDER_CREATE_SUCCESS

Step 5: create resources by cli

> txctl apply -f app.yaml
Done!

Step 6: list resources by cli

> txctl get applications
╔══════════════╗
║ Applications ║
╟──────────────╢
║ app01        ║
╟──────────────╢
║ app02        ║
╚══════════════╝

> txctl get subscriptions
-- Subscriptions --
╔══════════╤═════════════╤═══════════════════════╗
║ Source   │ Destination │ EventID               ║
╟──────────┼─────────────┼───────────────────────╢
║ app01    │ app02       │ ORDER_CREATE_FAILED   ║
╟──────────┼─────────────┼───────────────────────╢
║ app01    │ app02       │ ORDER_CREATE_SUCCESS  ║
╚══════════╧═════════════╧═══════════════════════╝

Usage as SDK

Install

npm install @ibm_wse/txrouter --save

Configuration

This module is working on RabbitMQ. You need to put your connection information into environment variables. The list of the environment variables list below:

Mandatory

  • TXROUTER.APPID: The application ID provided by TxRouter Services
  • TXROUTER.PROTOCOL: The protocol of RabbitMQ provided, now we support amqp and amqps
  • TXROUTER.HOST: Host name of RabbitMQ
  • TXROUTER.PORT: Port for communication with selected protocol
  • TXROUTER.USERNAME: Username (provided by TxRouter Services)
  • TXROUTER.PASSWORD: Password (provided by TxRouter Services)

Optional

Below environment variables required only for amqps protocol (with ssl/tls security)

  • TXROUTER.CERT.CLIENT: Client certificate
  • TXROUTER.CERT.KEY: Client key
  • TXROUTER.CERT.PASSPHRASE: Passparase of client key
  • TXROUTER.CERT.CA: Server certificate, commonly provided by RabbitMQ provider

As a publisher

const txrouter = require('@/ibm_wse/txrouter');
txrouter.send(event_id, message);

As a consumer

const txrouter = require('@/ibm_wse/txrouter');
txrouter.listen("target_app_id", {
        "event_id": msg => {
            // handler
        },
        ...
    }
)