pnxtech / hydra

A light-weight library for building distributed applications such as microservices
https://www.hydramicroservice.com
MIT License
645 stars 54 forks source link

SWIM membership protocol integration ?? #160

Closed skalyanapu-mtuity closed 6 years ago

skalyanapu-mtuity commented 6 years ago

Hi @cjus,

Instead of centralized services registry using, how about the integration SWIM membership protocol.

How far Hydra has these features ??If not is there plans for implementation?

Regards, Sai.

cjus commented 6 years ago

Hello @skalyanapu-mtuity

Good questions. Hydra is indeed production ready - as defined by companies which are successfully and significantly using Hydra in their own production environments. And there are perhaps more companies which use Hydra in smaller less critical areas of their infrastructure.

There are currently no plans to move away from Redis. To be honest, I see Hydra forking if it were to do so. And I don't see that as a bad thing. We feel there's a strong use case for Hydra as it stands.

Hydra has a very mature logging plugin based on Pino /logstash. https://www.npmjs.com/package/fwsp-logger

Have you looked at SenecaJS? http://senecajs.org/ It supports patterns and has SWM integration I believe.

Richard Rodger discusses it here: https://www.youtube.com/watch?v=67POODXANi8

@skalyanapu-mtuity do you have a use case where the things you're asking would be a serious deciding factor on whether or not to use Hydra? If so we'd like to better understand your needs.

skalyanapu-mtuity commented 6 years ago

Hi @cjus ,

We referred Seneca , before coming here. Hydra looks more flexible in creation of MS and maintenance than Seneca , few things we're looking for were does , Hydra have

These are some points we're considering right now , @cjus could you please provide your inputs ??

Regards, Sai.

cjus commented 6 years ago

@skalyanapu-mtuity sorry for the delay. We've just launched a major product at work. Hydra is a low-level library and many of the things you're looking for can be added as plugins. For example, auth libraries, logging and promises / async etc... We're currently focused on optimizations to Hydra but welcome community contributions.