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

microservice-lite

v1.0.3

Published

A lite framework for getting started with microservices

Downloads

21

Readme

microservice-lite

Build Status semantic-release

Microservice-lite is a very small package for getting started with microservices on node. It covers everything a simple microservice should have.

  1. Having it's own database (mysql, mongo, postgres, redis, and more)
  2. Small footprint
  3. Indepenent deployment
  4. Zero-configuration
  5. Zero-dependency
  6. Auto-discovery, fault toleranct and scalable

This works, thanks to the effort of @dashersw and his wonderful project cote.js and @balderdashy for writing waterline

install

# for pre-release do npm i -g microservice-lite@next
npm i -g microservice-lite

or

# for pre-release do yarn global add microservice-lite@next
yarn global add microservice-lite

cli commands

create a project

# creates new project
mslite new sample

responder

# New responder has been created as src/app/foo.responder.js
mslite g responder foo [...othernames]

requester

# New requester has been created as src/app/foo.requester.js
mslite g requester foo [...othernames]

Requesters are global and can be accessed from any location. The above can be accessed as FooRequester globally with the app

subscriber

# New subscriber has been created as src/app/foo.subscriber.js
mslite g subscriber foo [...othernames]

publisher

# New publisher has been created as src/app/foo.publisher.js
mslite g publisher foo [...othernames]

Publishers are global and can be accessed from any location. The above can be accessed as FooPublisher globally with the app

model

# New model has been created as src/models/foo.js
mslite g model foo [...othernames]

Models are global and can be accessed from any location. The above can be accessed as Foo globally with the app

database and adapters

Each microservice should have it's own database and mslite helps you with that. You could have a different database for each service. Eg mysql, mongodb, pouchdb etc.

By default, each project created with mslite comes with a disk based databased called sails-disk. There are other adapters you can use to have a different database like

  • sails-mysql
  • sails-postgresql
  • sails-mongo
  • sails-redis
  • sails-orientdb
  • sails-filemaker

see here for more info about adapters.

To add a different adapter for your project, simply install the appropriate adapter and make sure you have the database on your current machine as the adapter would try to make connection.

configure adapters

  1. Install required adapter eg.
npm i --save sails-mongo
  1. open config/adapters.js and require intalled adapter, also passing it an object name of your pleasing eg
module.exports = {
'sailsDisk': require('sails-disk'),
'sailsMongo': require('sails-mongo')
}

You can have any amount of adapters saved here for later use 3. Open config/connections.js create a connection object. Same as above, pass connection object to a name of your pleasing and specify the adapter from any defined in step 1

  module.exports = {
    'diskDb': {
      'adapter': 'sailsDisk'
    },
    myMongodbServer: {
      adapter: 'sailsMongo',//adapter's name, as defined above
      host: 'localhost',
      port: 27017,
      user: 'username', //optional
      password: 'password', //optional
      database: 'your_mongo_db_name_here' //optional
    }
  }
  1. Open cofig/models Tell your models to use the connection you want.
module.exports = {
  'connection': 'myMongodbServer', //change from diskDb
  'migrate': 'alter',
  'schema': true
}

test

NYD

examples

NYD

goal

The goal of the project is to make getting started with a microservice easy and painless, giving you basic features. The following features are on the roadmap

  • CLI for generating necessary files. eg
# generates a db model
mslite g model name [names...]
  • Easy connection to any database with the same api
  • .... got a feature in mind ? create an issue here

development

This project uses the following to keep things a bit sane around the house

  1. standardjs
  2. validate-commit-msg see http://conventionalcommits.org/
  3. Github flow

and is completly test driven TDD