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

event-sourcing

v0.0.2

Published

NodeJS Event-sourcing POC

Downloads

21

Readme

Event-Sourcing POC

Requirements

  • NodeJS (0.12)
  • AMQP compliant broker (tested with RabbitMQ)
  • Event storage (tested with MongoDB)

Installation

Include the node module in your project by installing it through npm:

npm install --save event-sourcing

Usage

The pattern is split up into two distinct parts. Publishers and Consumers. Publishers are responsible for persisting an incoming event and emitting it to consumers for process. Consumers listen for specific events and contain the business logic.

Publishers

Todo.

Consumers

Todo.

1.0 Roadmap

  • Usage examples
  • Interface storage to plug multiple engines (File based, SQL, Document)
  • Test with multiple AMQP brokers
  • Snapshot creation
  • Re-emit events support
  • Event replay
  • Event breakpointing