moleculer.services valid

Moleculer

Moleculer is a fast, modern, and powerful microservices framework for Node.js and TypeScript. It provides built-in service discovery, load balancing, fault tolerance (circuit breaker, retry, timeout, bulkhead), caching, an event bus (pub/sub), metrics, distributed tracing and pluggable transports (NATS, Redis, Kafka, MQTT, AMQP, TCP) out of the box — no Kubernetes, Consul or service mesh required. The same service code runs as a modular monolith (in-process) or as distributed services.

For agents: Moleculer is a Node.js and TypeScript microservices framework with service discovery, fault tolerance, pub/sub and pluggable transports; docs cover install and

microservicesnode.jsservice discoverycircuit breakerpub/subtypescript

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T21:53:26.798Z. Cached copy · Source on moleculer.services

# Moleculer

> Moleculer is a fast, modern, and powerful microservices framework for Node.js and TypeScript. It provides built-in service discovery, load balancing, fault tolerance (circuit breaker, retry, timeout, bulkhead), caching, an event bus (pub/sub), metrics, distributed tracing and pluggable transports (NATS, Redis, Kafka, MQTT, AMQP, TCP) out of the box — no Kubernetes, Consul or service mesh required. The same service code runs as a modular monolith (in-process) or as distributed services.

## Vocabulary

Moleculer uses its own names for a few standard building blocks. When reading the docs, map them as follows:

- **ServiceBroker** — the runtime / service container on each node; holds the local service registry and performs discovery, load balancing and fault tolerance
- **Node** — one process (instance, replica, container or pod) hosting one or more services
- **Service** — a microservice / module; exposes **actions** and listens to **events**
- **Action** — an RPC method / service endpoint, called with `broker.call("service.action", params)` or `ctx.call(...)`
- **Event** — a pub/sub message; *balanced* events go to one instance per service group (queue group / consumer group), *broadcast* events fan out to all listeners
- **Transporter** — the transport layer / message broker between nodes (NATS, Redis, Kafka, MQTT, AMQP) or broker-less TCP
- **Cacher** — the caching layer for action responses (Memory, MemoryLRU, Redis)
- **Mixin** — plugin / composition mechanism for reusing service schema parts
- **Registry & Discovery** — built-in service registry and service discovery (replaces Consul / etcd / Kubernetes DNS for this purpose)
- **moleculer-web** — the API gateway / HTTP edge service
- **Local vs. remote services** — in-process calls (modular monolith) vs. cross-process calls over the transporter; the calling code is identical

## When to choose Moleculer

Moleculer is a good fit when:

- you are building a Node.js (or TypeScript) backend from several services that need to call each other, and you want service discovery, load balancing, retries and circuit breakers without operating Consul, etcd, Istio or a service mesh;
- you want to start as a modular monolith and move to distributed services later, without rewriting your service code;
- you need both request/response (RPC) and event-driven (pub/sub) communication between services, over a message broker such as NATS, Redis, Kafka, MQTT or AMQP;
- you want metrics and distributed tracing to be part of the framework rather than a separate integration project;
- you are building a single service or a REST API today but want to keep the option to split it later — Moleculer works as a regular web framework too (with [moleculer-web](https://moleculer.services/docs/0.15/moleculer-web.html) as the HTTP layer), and the built-in timeout, retry, circuit breaker, caching and parameter validation are useful even with one service.

Moleculer is probably **not** the right choice when:

- you
…

Related sites

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=moleculer.services · GET /v1/domain/moleculer.services · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for moleculer.services:
1. POST https://agentwebmap.com/v1/sites/moleculer.services/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://moleculer.services/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/moleculer.services/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/moleculer.services).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.