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

@fidtech-sa/segbird

v1.0.0

Published

A simple tool that abstracts http requests between microservices into simple events using a publish-subscribe scheme

Downloads

5

Readme

Segbird

Introduction

This is a prototype for abstracting http messages between microservices into simple events using a publish-subscribe scheme.

Requirements

  • Loopback 2.x or 3.x. Ideally, it would be great to have only Express as a dependency.

Main Features

  • Endpoints standardization.
  • Automatic authentication using JWT.
  • Abstraction layer using a publish-subscribe scheme.

Usage

For this example, we will have two microservices:

  • Microservice A: http://microservice-a.com
  • Microservice B: http://microservice-b.com

Objective: Microservice A needs to send a message to Microservice B.

Microservice A (publication):

Create a boot script called "segbird.js". Require and initialize Segbird.

/server/boot/segbird.js

const segbird = require('segbird');
module.exports = (server) => {
  segbird.init({
    server, // The Loopback server instance
    services: { // A list of microservices that will be used as a target to publish messages
      B: 'http://microservice-b.com',
    },
    jwtSecret: 'mySuperSecretKey', // A secret key the will be used to sign JWT requests
  });
};

Wherever you want, publish a message to Microservice B.

/server/models/user.js

const segbird = require('segbird');

module.exports = (User) => {
    const functionThatWillTriggerEvents = async () => {
        await segbird.publish('myCustomEvent', 'B', {name: 'John Doe'});
    };
};

Microservice B (subscription):

In microservice B, create a boot script called "segbird.js". Require and initialize Segbird. After this, subscribe to the event that Microservice A will publish.

/server/boot/segbird.js

const segbird = require('segbird');
module.exports = (server) => {
    segbird.init({
        server, // The Loopback server instance
        jwtSecret: 'mySuperSecretKey', // The same JWT secret you used to initialize Segbird in Microservice A. It will be used to verify incoming requests.
    });
    segbird.subscribe('myCustomEvent', async (data) => {
        console.log(data) // {name: 'John Doe'}
    });
};

Note: You must initialize Segbird with the same JWT secret that you used in microservice A.