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

microx

v0.3.3

Published

Micro-services framework for Node.js

Downloads

5

Readme

microX npm version

Microservices framework for Node.js

UNDER DEVELOPMENT

microX is under ongoing development. Breaking changes may occur at any time until the first stable version will be released.

BREAKING CHANGE - starting from version 0.3.0 and above the module exports a factory method like most framework, where in version 0.2.* and lower the class Service was exported directly.

What is microX?

Microservices architecture adaptation is growing every day, making the agile development process easier and more productive but comes with a cost - each service is simple, but managing an entire eco-system of microservices is not a walk in the park. There are many known and highly adapted solutions, such as Sensca, but when I started my journey with microservices I wanted to develop my own framework, for deeper understanding of the mechanics of microservices.

This project is for self learning experience, but after it will be completed, I will give it a test run on a production project. Sure, it is not the fastest as it is built on top of HTTP using express framework (TCP based frameworks are much faster), but the simplicity of using it and scaling it makes it a good tool for rapid development.

Basic Architecture

microX is based on a pub - sub protocol using Redis for service discovery. Instead of having a central registry service that holds all the services locations, each time a service is going up is publishes itself to all the other services. Each service in that case holds a complete map of the services eco-system, making the central registry redundant and making each service more de-coupled from others. The only dependency for each service is the Redis server location.

A service can call other services by their name & version. When a service calls another service, it perform the communication directly with the service according to the service map it holds. This can improve performance over a standard broker based solutions, where the broker receives the calls and performs the forwarding to the required service, causing each call to go through at least 2 servers, where in microX once a service knows the location of another service, it contacts it directly.

Docs

Documentation is still a work in progress, but partial documentation can be found here.