// the find
moleculerjs/moleculer
:rocket: Progressive microservices framework for Node.js
Moleculer is a Node.js microservices framework that gives you service discovery, load balancing, fault tolerance, and inter-service communication out of the box. It runs as a broker-based system where nodes discover each other and call actions across the mesh. Aimed at teams building distributed Node.js backends who want Rails-style batteries-included rather than assembling these pieces from Kubernetes + gRPC + a service mesh.
Built-in circuit breaker, retry, bulkhead, and timeout middlewares are wired in and configurable per-action — you don't write this yourself. Transporter abstraction (NATS, Kafka, Redis, AMQP, raw TCP) means you can swap message brokers without touching service code. The pluggable cacher with Redis and LRU-memory backends integrates at the action level, not the application level — cache a result by adding one line to the action schema. Metrics and distributed tracing (Jaeger, Zipkin, Prometheus, Datadog) are first-class, not bolted-on.
TypeScript support is declarative-schema-based, which means autocomplete and type inference on action params and return types is weak — you get types for the framework but not for your own service contracts. The masterless gossip-based topology works fine at small scale but becomes operationally opaque at larger node counts; there's no built-in visibility into the cluster state beyond what you wire up yourself. Last commit March 2026 and 6k stars is modest for a framework of this scope — the ecosystem of third-party modules is thin and several official modules (moleculer-db, moleculer-web) lag behind the core in maintenance. No schema-first service contract enforcement: nothing stops a caller from passing malformed params at the topology boundary and the fastest-validator integration fires at runtime, not compile time.