steedos-server-moleculer

Embed a Moleculer broker in NestJS to orchestrate Steedos microservice communication.

1.6k|413|Updated Mar 4, 2019
One-click install
npx skills add https://github.com/steedos/steedos-platform --skill steedos-server-moleculer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: steedos-server-moleculer
Source: https://github.com/steedos/steedos-platform/tree/main/skills/steedos-server-moleculer
Command: npx skills add https://github.com/steedos/steedos-platform --skill steedos-server-moleculer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Steedos Server requires a scalable, self-contained microservice orchestration layer; embedding a Moleculer broker enables reliable cross-service communication, event routing, and dynamic service loading within the Steedos platform.

Core Features & Use Cases

  • Embedded Moleculer broker integrated with NestJS to power microservice communication.
  • Event handling for metadata, package loading, and service lifecycle.
  • Dynamic service loading for community and enterprise editions; robust inter-service calls with broker.call, broker.emit, and broker.broadcast.

Quick Start

Start the Steedos server with Moleculer integration enabled and verify the broker connects to the Redis transporter.

Frequently Asked Questions about steedos-server-moleculer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate microservices communication in a NestJS-based Steedos deployment?

The Moleculer broker powers inter-service communication in Steedos through broker.call for direct requests, broker.emit for targeted events, and broker.broadcast for system-wide notifications across all registered microservices.

How does event handling work for metadata and package loading in Steedos microservices?

Event handling in Steedos microservices leverages the Moleculer broker to route metadata and package loading events. The AppMoleculer service manages dynamic service loading, ensuring proper lifecycle management across community and enterprise editions.

Do I need Redis to configure the transporter and caching for the Steedos Moleculer broker?

Configuring the Steedos Moleculer broker requires setting up a transporter such as Redis, along with namespace and caching configurations. This enables self-contained microservice orchestration and reliable cross-service communication.

What is the best way to handle service discovery and dynamic service loading in Steedos?

The embedded Moleculer broker provides service discovery and dynamic service loading for Steedos, supporting both community and enterprise editions. It handles broker.call, broker.emit, and broker.broadcast operations within NestJS-based deployments.

Can I use broker.emit and broker.broadcast for event routing across Steedos microservices?

Yes, broker.emit and broker.broadcast handle event routing across Steedos microservices. The Moleculer broker manages namespace, transporter, and caching configurations to deliver events reliably for metadata and package loading operations.