verdaccio
Moleculer
Our great sponsors
verdaccio | Moleculer | |
---|---|---|
8 | 16 | |
15,864 | 6,016 | |
0.7% | 0.9% | |
9.7 | 7.5 | |
about 15 hours ago | 1 day ago | |
TypeScript | JavaScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
verdaccio
- verdaccio v5.20.1 has been rolled out
-
3rd party package repositories?
do you know the project https://github.com/verdaccio/verdaccio
-
đŚ Everything you need to know: package managers
Verdaccio allows to setup a private proxy registry for Node.js
-
Npm link doesn't work with React Native, what do you use for testing local modules?
Verdaccio does okay for this
-
Hosting my own node_modules
Thereâs also this: https://www.npmjs.com/package/verdaccio
-
Self-Hosted Private Registry
Cool! What makes Package Depot better than existing solutions such as verdaccio?
-
Monorepo or not?
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...
-
Researcher hacks over 35 tech firms in novel supply chain attack
The goal of verdaccio is to make this less complicated. https://github.com/verdaccio/verdaccio
Moleculer
-
Make microservices look like monoliths
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.
-
How to Import/Reference a Microservice from another one
If youâre using k8s, check out https://moleculer.services and this would likely solve what youâre looking for.
-
Node JS Microservice Frameworks for Developing Scalable Web Apps.
Molecular â Progressive Microservices Framework for Node.js
-
First time building microservice-based application
While youâre delving into microservices, check out Moleculer https://moleculer.services
-
if Nodejs does not meant for CPU intensive tasks so I think it's better to avoid it from the beginning
I almost canât believe I havenât seen it mentioned here before, but adding Moleculer into your node project (if itâs clustered/k8sâd) will literally solve many single threaded problems, not to mention tons of other scalability issues. https://moleculer.services/
-
How to deal with singletons in a distributed system?
You could use a framework for this. Have a look at moleculer
-
Where can I learn to implement microservices?
I haven't used this, but it seems neat: https://moleculer.services/
-
Microservices using express js
Look into Moleculer.
-
Been playing with moleculerjs recently, and just finished my first package: a service that allows you to use any node API framework as a moleculer gateway.
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.
-
Donât start with microservices â monoliths are your friend
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.
What are some alternatives?
yalc - Work with yarn/npm packages locally like a boss.
Nest - A progressive Node.js framework for building efficient, scalable, and enterprise-grade server-side applications with TypeScript/JavaScript đ
registry-sync - synchronize selected packages from a remote npm registry
Express - Fast, unopinionated, minimalist web framework for node.
AWS Lambda Router for NodeJS - AWS Lambda router for NodeJS
artifactory-pypi-scanner - Saves you from package injection!
seneca - A microservices toolkit for Node.js.
AdonisJs Framework - AdonisJS is a TypeScript-first web framework for building web apps and API servers. It comes with support for testing, modern tooling, an ecosystem of official packages, and more.
dawson-cli - A serverless web framework for Node.js on AWS (CloudFormation, CloudFront, API Gateway, Lambda)
fastify - Fast and low overhead web framework, for Node.js