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

polyservice

v1.1.0

Published

The easiest way to write microservices. Focus on business logic not boilerplate!

Downloads

24

Readme

Polyservice

The easiest way to write microservices

NPM version

Focus on writing business logic not boilerplate for your microservices!

What is polyservice?

Polyservice is an extremely lightweight and fast way to write business logic that needs to run in multiple environments with many IO controllers. Meaning the same function(s) can be used for a web API, CLI tool and a socket.io application with little to no extra code modifications.

The goal of Polyservice, aside from being unopinionated about your project's structure, is to make writing microservices extremely fast by abstracting out the setup and boilerplate without removing any control from the developer.

Polyservice is not just for microservices! Polyservice can easily be set up for monolithic applications as well, it all depends on your use case.

Installation

NPM

polyservice is available through the npm registry

$ npm install polyservice

Features

  • Robust controller system
  • Built in type checking for incoming data
  • Expandable plugin system
  • Modular design
  • Plug-n-play approach for IO controllers and middleware

Features in development

  • Auto generated client libraries
  • Auto generated documentation

Quick start

The quickest way to jump int writing services is to use one of the existing "poly controllers" for this guide we will be creating a web service using the polyexpress controller

  • installation npm install polyexpress
  • this controller is a wrapper for the express framework

Creating a service

We start by creating a service object, this object will define the name of your service an array of method objects, which we will do in the next section Creating your methods, and a controller or an array of controllers in which your service will be used by

import { service } from "polyservice";
import { web } from "polyexpress";

const myService:service = {
  name: "myservice",
  method: [ echo ],
  controller: web
}

Creating your methods

The polyservice framework uses an interface called method to define the basic structure of your service method objects controllers will expand this interface with additional information needed for that controller

In this example we are using the webMethod since we are writing a http api. Other controllers may use their own method interface to use more than one interface please refer to the following typescript code const someMethod:webMethod & othercontrollerMethod = {}

the arguments key is an optional key and uses an object of polyargs which can be extended by controllers that require additional information

import { result } from "polyservice";
import { requestMethod, webMethod, requestType } from "polyexpress";
const echo:webMethod = {
  name: "echo",
  request: requestType.POST, // required for web controller
  arguments: {
    input:{ type:"string", requestMethod: requestMethod.PARAM } // requestMethod is required by the web controller
  }
  callback: function(input:string):result{
    const response:result = {
      code: 200,
      message: input
    }
    
    return result;
  }
}

Registering your service

In the entrypoint of your code Here we are using polyservice's built in HttpListener singleton however you can use your own node.js Http or Https server if desired.

import { polyservice, HttpListener } from "polyservice";
(() => {

  polyservice.register(myService);
  polyservice.init({ httplistener: HttpListener.createServer } /** params to pass to the controller objects on init **/);
  
  HttpListener.Instance.Listen(process.env.PORT || 3000);

})();

Good Job!

You should now have a running http server with an endpoint at localhost:3000/myservice/echo/MESSAGE

Full Documentation

the full documentation can be found on the Wiki

Additional Polyservice controller packages includes the following

-- Still in development --

Future plans

This framework is actively being developed and you can follow the progress right here on github