verdaccio VS Moleculer

Verdaccio allows to setup a private proxy registry for Node.js

Verdaccio does okay for this

I highly recommend using a package proxy like https://github.com/verdaccio/verdaccio instead of git submodules if you have more then one developer using your code/repo. Biggest factor is the cost of the developers time. Why teach them a different way to install dependancies when there is a standard way of doing things your CI/CD is simplified, the knowledge of git submodules is good to know, but this is now tribal knowledge on how to setup this up, update dependancies, etc...

The goal of verdaccio is to make this less complicated. https://github.com/verdaccio/verdaccio

My goto for this kind of task is moleculer: https://moleculer.services/

Fast, battle tested, vue2-like approach, great documentation, good community. The automatic indipendent-scalability as an option is usually the main selling point of these solutions, but honestly I think the real pro is the "composition" approach, which is essential if you want to keep a clean and well-organized codebase. On this regard, I found moleculer pretty great even for large teams.

Molecular – Progressive Microservices Framework for Node.js

While you’re delving into microservices, check out Moleculer https://moleculer.services

You could use a framework for this. Have a look at moleculer

Look into Moleculer.

Moleculer already provides an in-house http gateway, but what if you want to use an existing API, and how to maintain decoupled code when creating your gateway? This package solves both. You can create your API, passing in any services you require as dependencies. You can then bind your API to moleculer using the moleculer-universal-gateway.

But there's more to the topic of microservices. Seems like all the conversation focuses on deployment pain. You can build a service with something like Akka or Moleculer where the modules act independently and have some message passing and resilience from each other, but they can still all live in one codebase, one process, and deployed as one unit. It works fine and isn't painful at all. And maybe down the line you decide to split the thing up into multiple processes and multiple deployment units, and that's an easy refactor because the modules are already somewhat separated.

Moleculer - Fast & powerful microservices framework.

I'm a fan of https://moleculer.services/

Our work project has outlived it's MVP life-cycle nature and we have decided to move away from currently used NestJS framework to https://moleculer.services/ in a manner of fairly extensive and aggressive refactor.