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

samsa

v0.0.3

Published

A microservices library with req-rep and pub-sub and streams, oh my.

Downloads

18

Readme

samsa

A microservices library with req-rep and pub-sub and streams, oh my.

Quick look

samsa = require 'samsa'
hello_methods =
    sayHello: ({name}) -> "Hello, #{name}!"
hello_service = new samsa.Member 'hello', hello_methods
samsa = require 'samsa'
hello_client = new samsa.Member
reply = await hello_client.request 'hello', 'sayHello', {name: "Jeffrey"}
assert reply == "Hello, Jeffrey!"

Architecture

Samsa builds upon Kafka producers and consumers to enable easy request-reply and pub-sub between microservices. All this is encapsulated in a single Node class, which may or may not be named.

A named Node acts as both a Service and a Client. As a Service it listens for requests and events to act on, and sends replies or errors back as necessary. An unnamed Node can act as a Client only, sending requests or publishing events to listening Services.

What that means in Kafka

  • Each Node acting as a Service (that is, it has a name) consumes a Kafka Topic of the same name.
  • Requests and Events are sent to services by name, so they use a Kafka Producer to add messages to that Topic.
  • Replies are sent on a Topic suffixed "-reply", i.e. the "hello" Service sends replies on the "hello-reply".

All Services act as part of the same Kafka Consumer Group, so they receive a balanced subset of requests.

Thanks

This Node.js implementation is written around kafka-node.