How Pandora.js Service Mechanism Enables Efficient Process Orchestration and RPC

This article is part of a series introducing Pandora.js and focuses on its Service mechanism, a high‑level process orchestration feature for Node.js applications.

Service solves what problems?

It provides a way to manage expensive processes, offering middleware management, standardized start/stop flows for RPC providers, and isolation of services that need coordinated lifecycle handling.

Basic principles

Simple, easy‑to‑use interfaces.

Unified startup process.

Asynchronous start and stop.

Processes are costly, so reuse is important.

Core capabilities

async start()

interface. async stop() interface.

Structured logging and configuration.

In‑process startup order management.

Service definition

Service consists of two parts: the chain definition syntax in procfile.js and the implementation of the Service interface.

Example: RPC Provider

The article walks through creating a basic Etcd service and an RPC Provider named TryRpc. It shows how to register the service in etcd, expose JSON‑RPC methods, and implement standard start and stop logic with heartbeat registration.

module.exports = class Etcd extends NodeEtcd { /* ... */ };

class TryRpc { /* ... */ async start() { /* register, start HTTP server */ } async stop() { /* deregister, stop server */ } };

Running pandora dev starts the processes, registers the RPC service in etcd, and logs the listening address. Stopping the application cleanly removes the registration and stops the HTTP server.

Consumer example

A simple web process discovers the RPC service via etcd, picks a node, creates a Jayson client, and invokes methods such as add and mul through an HTTP query.

The article concludes with a preview of the next topic on inter‑process communication and mentions that the Service model is now fully covered.