npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@darlean/base

v2.0.0-alpha.18

Published

Base types and definitions for creating Darlean actors and suites

Downloads

40

Readme

Introduction

The @darlean/base package provides the types that are required to create and expose custom actor suites.

Installation

$ npm install @darlean/base

Usage

Defining an actor

A simple actor with only one action method that just echoes back the received message can be created as follows:

import { action, ActorSuite, IActorSuite } from '@darlean/base';

export const ECHO_ACTOR = 'demo.EchoActor';

export interface IEchoActor {
    echo(value: string): Promise<string>;
}

class EchoActor implements IEchoActor {
    private name: string;

    constructor(name: string) {
        this.name = name;
    }

    @action()
    public async echo(value: string): Promise<string> {
        return `${this.name} echoes: ${value}`;
    }
}

Some remarks:

  • For creating actors, we no not need the heavy @darlean/core library. Just the light-weight @darlean/base is sufficient for this.
  • The exported interface IEchoActor can be used by code that wants to invoke action methods on our actor without requiring a dependency on the implementing class (EchoActor). In our simple example this would not matter, because the class does not have external dependencies, but when the actor class would depend on a lot of external packages, it would be inconvenient and undesirable for code that wants to invoke the actor to also become dependent on these dependencies, especially when it is remote code that runs in another process that does not already have these dependencies.
  • The exported string ECHO_ACTOR = 'demo.EchoActor' makes it possible for code to retrieve (discover) the actor.

Defining a suite

Related actors are grouped together into suites. Based on the above actor, it is trivial to define the corresponding suite:

export function createEchoSuite(): IActorSuite {
    return new ActorSuite([
        {
            type: ECHO_ACTOR,
            kind: 'singular',
            creator: (context) => {
                const name = context.id[0];
                return new EchoActor(name);
            }
        }
    ]);
}

This creates a new actor suite with the definition of one actor (namely our echo actor), which is defined as a singular, has demo.EchoActor as actor type, and has a creator function that derives the name of the actor by taking the first element of the actor's id, and passing that to the constructor of EchoActor.

Actors, suites, packages and applications

Actors

Actors play a key role in Darlean. Actors are objects that can be invoked remotely and that have a private state (often grouped together in one object to simplify persistence) and published (remotely invokable) action methods that perform actions and/or modify the internal state.

Action methods are plain methods decorated with @action (or, for more advanced use cases, @timer, @activator or @deactivator.

Actors have a type (called 'actor type'), which is a string. It is recommended to use a dotted namespace notation to avoid name collisions, like myorganization.MyActor.

Actors can be singular and multiplar. A singular actor is guaranteed to only be active at most once at any moment within the entire cluster. A multiplar actor can be active multiple times within the entire cluster.

Suites

Related actors can be grouped together in a suite. So, a suite is just a collection of actor types that together provide one specific bit of functionality, like the management of a shopping cart or user administration.

A suite usually consists of a single creator function that receives configuration parameters as arguments, and then creates, fills in and returns an IActorSuite structure. This structure contains a list of actor definitions. Each definition contains the actor type, the kind (singular or multiplar) and an actor creator function.

The actor creator function is responsible for creating new actor instances. It is basically a factory function for actors.

Because the logic of creating actor instances is contained within the returned IActorSuite, it is not necessary to export the actors themselves (they can be "private" to the module). Just exporting the suite creator function is sufficient for other parts of the application to use your actors.

Packages

When suites are to be used by other packages, they can be exported as a regular TypeScipt package. Unlike ordinary packages, where the actual functions and objects that do the work are exported, for suite packages only the suite creator function needs to be exported. The reason is that the IActorSuite returned by the suite creator function already knows how to instantiate new actor objects.

In addition to exporting the suite creator function, it is useful to also export the interfaces (usually interface types) and actor types (string types) of all actors that are meant to be invoked remotely. These two pieces of information are sufficient for code to retrieve (discover) and invoke actors.

Applications

When actors are created, grouped into suites and optionally packed into packages, it is necessary to instantiate an ActorRunner (typically by means of a ConfigRunnerBuilder) to which the suites can be registered. The actor runner takes care of the networking and other administration required to make actors discoverable by other applications and to handle action requests to actors that it hosts (that is, that are part of suites that are registered to the runner).

The creation of such applications is not part of this library, because it would add a lot of dependencies to this base library that are not required for just writing actor suites.

To read more about creating Darlean applications that host registered actor suites, see the @darlean/core (GitLab|NPM) package.

See also

  • Package @darlean/core (GitLab|NPM) which explains how to create Darlean applications that host exported actor suites
  • A minimalistic example application that uses the above mentioned echo actor.
  • The Darlean Tutorial in which we illustrate step by step how to build a real distributed oracle that answers questions like 'How warm is it tomorrow?' and 'What is the price of milk?'.
  • The Darlean Documentation on our website.
  • The API Documentation for @darlean/base.