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

@escueladigital/micro

v3.4.37

Published

Microservice manager for nodejs with kafka

Downloads

39

Readme

Alt Text Pendragon

Open source simple microservice manager for nodejs

Install

npm install pendragon

Estructura del projecto

 api
   | config
       | communication.js
       | routes.js
   consumer
       | consumerName.js
   controllers
       | controllerName.js
   events
       | microName
            | consumerName.js
   schemas
       | schemaName.js
    helpers
       | index.js
config/

communication.js

module.exports = [];
/* 
  En caso de que se tenga que se necesite comunicación entre microservicios se tiene que exportar el arreglo con el nombre del servicio por ejemplo
  
  module.exports = ['servicename','servicename2'];
  */

routes.js

/* 
Exportar el objeto de rutas posibles de la api, en este caso el contralador debe de existir así como la accion en el controlador del mismo.
*/
module.exports = {
  'GET /version': {
    controller: 'index',
    action: 'version'
  }
};
/*
Si no se desea exportar un ruta simplemente exportar
module.exports = {}
*/
consumer/

example.js

const { micro } = require('@escueladigital/pendragon');

module.exports = {
  getById: async req => {
    const payload = await micro.app.models.actividadespropuestas.findAll({});
    return payload; // return all data
  }
};

req el parametro req contiene bastante información así como los parametros de graphql

En este caso los modelos que son generados en el apartado de schemas y son inyectados en el objeto app y podemos usar los métodos de mongoose como findOne o find.

Al final es importante retornar el resultado, todos los métodos en los consumer son de retorno.

Los métodos adicionales deben ubicarse en la siguiente ruta: