moleculerjs/moleculer

:rocket: Progressive microservices framework for Node.js

View on GitHub ↗Jump to charts ↓

moleculerjs/moleculer has 6k+ stars and 600+ forks on GitHub, is written in JavaScript, and was last pushed on Sep 7, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 28 minutes ago
Added to GitGenius on September 10th, 2026
Created on February 17th, 2017
Open Issues & Pull Requests: 82 (+0)
GitHub issues: Enabled
Number of forks: 605
Total Stargazers: 6,379 (+0)
Total Subscribers: 122 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 12.5 days
Mean response time: 148.7 days
90th percentile: 200.5 days
Tracked items: 28

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 19
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 694 days
Stale 30+ days: 17
Stale 90+ days: 17

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • Module: Transporter (2)
  • Type: Enhancement (2)
  • help wanted (2)
  • Breaking changes (1)
  • Module: Core (1)
  • Module: Runner (1)
  • Priority: Low (1)
  • Status: Available (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Moleculer is a microservices framework for Node.js that enables developers to build distributed systems with a focus on progressive adoption and scalability.

The framework addresses the complexity of building microservices by providing built-in support for service discovery, load balancing, and inter-service communication. It works by allowing developers to define services as isolated units that communicate through a message broker, with the framework handling routing, serialization, and fault tolerance automatically. The approach supports both local development and distributed production deployments without requiring code changes.

Moleculer suits teams building systems that need to scale from monolithic applications to distributed architectures incrementally. It works well for projects where services need to communicate reliably across network boundaries and where operational concerns like service discovery and load balancing should be handled by the framework rather than custom code. The framework is particularly valuable for Node.js shops that want microservices capabilities without the overhead of heavier orchestration platforms.

Development on the project shows consistent activity with regular updates and maintenance. The codebase receives ongoing improvements and bug fixes. The project maintains active engagement with its user community through issue tracking and documentation updates. The framework continues to evolve with enhancements to its core messaging and service management capabilities.