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

evilcluster

v1.0.2

Published

nodejs cluster manager

Downloads

5

Readme

evilcluster

Node.js CI npm version MIT Licence Dependency Status

Monolithic approach of nodejs clustering.

What ? why ?

Sometime, you can make the choice to not have a microservice architecture :

  • when you "pkg" (https://github.com/zeit/pkg) your nodejs application
  • when the logic of microservices is not "appropriated" ( ... )
  • when you want to have only one "Windows Service" (see https://nssm.cc/) with all your modules inside

Best practice microservice design

Below a classical design of microservices running on the same box.

Usually, master processes and forks talk each other using IPC (process.send). Only a boolean (cluster.isMaster) is available to handle code running in forks vs master process.

Process 1 can not speak natively with process 2 unless if you implement it, a kind of gateway between them (webservices, websockets, tcp, redis, ...). This is a best practice because of scalability and deployment facility.


  process 1
      │
      │
 cluster.fork()
      │
      ├──── fork 1
      │
 cluster.fork()
      │
      └──── fork n


  process 2
      │
      │
 cluster.fork()
      │
      ├──── fork 1
      │
 cluster.fork()
      │
      └──── fork n

Monolithic design approach

Now, if you NEED to NOT have many different standalone processes, you are thinking about a monolithic architecture, and you will have to find a way to monitor spawned processes, speak between master/spawns/forks processes, handle logs, ...

This (poc) module aims at a pseudo monolithic architecture. The main process SPAWN workers. Then spawned workers MAY FORKS.

So:

  • cluster.isMaster is true when it's the main process
  • cluster.isSpawn is true when it's a spawned worker
  • cluster.isFork is true when it's a fork of a spawned worker
    main process
          │
          │
 child_process.spawn()
          │
          ├───────── worker 1
          │             │
          │        cluster.fork()
          │             │
          │             ├──── fork 1
          │             │
          │        cluster.fork()
          │             │
          │             └──── fork n
          │
 child_process.spawn()
          │
          ├───────── worker 2
          │             │
          │        cluster.fork()
          │             │
          │             ├──── fork 1
          │             │
          │        cluster.fork()
          │             │
          │             └──── fork n
  child_process.spawn()
          │
          ├─────── worker 3 (no fork wanted)
          ¦
          ¦

Real example:

        my app
          │
          │
          ├── webserverFrontend
          │          │
          │          ├──── fork 1
          │          │
          │          └──── fork n
          │
          ├── webserverApi
          │          │
          │          ├──── fork 1
          │          │
          │          └──── fork n
          │
          ├── inMemoryDatastore (only one master process)
          │
          └── backgroundTaskManager ...

Inter-processes communication

(DOC/TODO)