by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Dustin Deus
    @StarpTech
    Hi @leolower I don't know if I understood your use case correctly. Could visualize it or rephrase your question?
    @blanchma duration is returned in nanoseconds but it this will be refactoed as well in https://github.com/hemerajs/hemera/pull/236/files
    Dustin Deus
    @StarpTech
    @rualatngua meshes are awesome but in most of the uses cases overkill! Zeronode based on zeromq which has to be nativly build. I build hemera to reduce complexity and maintainance. I will never use seneca anymore.
    InternalServerError
    @InternalServerError
    Hi there, I'm new on hemera/node development. So thank you for your work on hemerajs which looks like really amazing ! However questions :)
    1/ I would like to pub some message on node (hemera btw) and got it on front framework (e.g Angular) through NATS. Is it possible ?
    2/ I tried to call several microservices on Hapijs handler, but in vain, it always returns me (Promise <pending>) or (Object [object]) whereas when I just return the req.act(...) I have the correct response, any idea please ?
    InternalServerError
    @InternalServerError

    Typically my use case :

    • Web access to my url : https://my-amazing-url.com/profile which is generate with front js framework
    • Each component of this page is calling a microservice through NATS pub/sub system

    Is it the good way to do it ?

    Dustin Deus
    @StarpTech
    Hi @InternalServerError it's very hard to answer your questions because it sounds very general but If you want to call hemera from frontend you have to implement a HTTP api-gateway at first. You can use hapijs or fastifyjs for both we provide plugins.
    Your use case is standard when I assume you don't want to call NATS directly from the frontend.
    InternalServerError
    @InternalServerError
    Hi @StarpTech huumm I see thank you ! I'd expect to be able to call NATS server directly from Angular, but it seems to be not the usecase, I am sorry but I am new on node ecosystem and have to build a complex app, very funny but little bit hard (I'm from PHP's Symfony which is pretty different).
    I base my tests from hemerajs/aither with the redis/nats/hapi/hemera stack.
    I have unfortunately many troubles (like hapi's handler returns with many hemera.act for x microservices calls in handler), but the frameworks glue through NATS seems to be my main trouble.
    My other one is apparently node-nats seems to not be compatible with Angular 7, so I'll maybe go full hemerajs with template engine like Blaze for frontend ...
    and @StarpTech thanks again for your work, I started on another microservices node framework, but I found hemera really more easy to work with at first sight
    Dustin Deus
    @StarpTech
    @InternalServerError I hope you didn't require hemera or nats in angular. This is completly wrong. Hemera was designed for node.js only.
    Dustin Deus
    @StarpTech
    veeramarni
    @veeramarni
    @StarpTech We are thinking of creating a plugin (kind of center piece) to register how many hemera servers are active and deactive. Sort of like lifecyle states to monitor existing end points in the hemera. Wondering if you can throw some ideas where to begin with?
    Dustin Deus
    @StarpTech
    The hemera-clip can provide a list of all active services.
    If you just need a simple list you could use the gnats REST api
    But this shows only the active connections not the hemera actions. It depends on your needs.
    1 hemera instance = 1 connection
    veeramarni
    @veeramarni
    @StarpTech To better illustrate my situation, we have A, B and C hemera servers. A need to know when B and C are up so it can send configuration to them. Looks like hemera-stats is what i need. Thanks for your help.
    Dustin Deus
    @StarpTech
    @veeramarni When B/C relys on A I think its better not to split them? In NATS you can't check if any service is available expect that you will receive a timeout.
    You have multiple ways:
    1. Host everything in one service
    2. Ping for such services with a smaller timeout
    3. Use nats-streaming plugin so all requests will be redelivered as soon as the service is up
    veeramarni
    @veeramarni
    I think option 3 would suits us. Basically each element A or B or C can start independently. But configuration is what would changes based on the what exist in the environment etc.For example if A know B available, it would change its configuration and hand off some work to B instead of A taking that responsibility.
    in my case, i just only need to know when B or C are available. I still think hemera-stats would help.
    veeramarni
    @veeramarni
    let me know your feedback on hemerajs/hemera#237
    Dustin Deus
    @StarpTech
    Hi @veeramarni please check the PR
    Kevin Clough
    @KClough
    @StarpTech is it possible to use both hemera-snappy and hemera-msgpack? If so, would you reccomend it?
    We have some handlers that pass large objects + buffers and are looking at all options to optimize.
    Looks like hemera-snappy is no longer in the packages folder, was it deprecated?
    Felipe Barros Cruz
    @FelipeBarrosCruz
    Hello everyone.
    Please someone knows a plugin to stream the hemeralogs to a database or logstash, or some way to get the raw event logs in Hemerajs?
    pward123
    @pward123
    what version of nats server is recommended with hemera 7.0.1? does it work with nats 2.0.0?
    Mark Miller
    @momiller121
    Hello - is anyone developing Hemera on a non-Windows platform? We can run the hemera project tests on Windows but are facing some issues on a *nix platform related to starting and stopping NATS via the HemeraTestsuite. We're just curious if we're doing something uniquely wrong or if this has been observed by others. Thanks!
    Federico Aloi
    @faloi

    Hi there! I'm trying to catch some specific errors in the setErrorHandler and return a valid response instead of an error - my plan is to catch joi validation errors there and return a non-error response. I believe setErrorHandler doesn't have the ability to convert the response to a non-error, am I right?

    Also, I believe the docs are wrong, because in the code setErrorHandler accepts 3 arguments (hemera, error, reply) but in the docs only one is mentioned (error).

    This is my code:

    hemera.setErrorHandler((hemera, error) => {
        return new Promise((resolve, reject) => {
          if (error.isJoi && error.name  === 'ValidationError') {
            resolve({ error: true, message: {error: error.message }, status: 422 });
          } else {
            reject(error);
          }
        });
      });
    cwilso03
    @cwilso03
    Hi @StarpTech, I recently upgraded a project I'm working on to Hemera 7.0.1, and am getting some dependency warnings in the output of yarn install. Are there plans to update the following dependencies?
    Here's the output from yarn:
    warning hemera-joi > joi@12.0.0: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
    warning hemera-joi > joi > topo@2.0.2: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
    warning hemera-joi > joi > hoek@4.2.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
    warning hemera-joi > joi > topo > hoek@4.2.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
    warning nats-hemera > joi@11.1.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
    warning nats-hemera > joi > hoek@4.2.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
    warning nats-hemera > joi > topo@2.0.2: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
    warning nats-hemera > heavy@4.0.4: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
    warning nats-hemera > heavy > hoek@4.2.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
    warning nats-hemera > heavy > joi@10.6.0: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
    warning nats-hemera > heavy > joi > hoek@4.2.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).

    Continued, since it wouldn't let me paste everything in one post:

    warning nats-hemera > heavy > joi > topo@2.0.2: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
    warning nats-hemera > heavy > boom@5.2.0: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
    warning nats-hemera > heavy > boom > hoek@4.2.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
    warning nats-hemera > heavy > joi > items@2.1.2: This module has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version of hapi to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).

    Also, I get this warning, too:

    warning " > nats-hemera@7.0.1" has incorrect peer dependency "nats@>= 0.8.x <= 1.2.x".

    However, my project does seem to work fine with NATS server version 2.0.4.

    Vladimir Djukic
    @vforv
    Hello @StarpTech
    Is it hard to upgrade to last hemera version
    ?
    This is last version we used:
    "nats": "^0.7.20",
    "nats-hemera": "^2.1.6",
    "hemera-mongo-store": "^2.0.1",
    "hemera-stats": "^2.0.1",
    Richard Scappaticci
    @Richard-Scap
    Is this room still active?
    We are having a difficult time getting herma to play with hemera-ajv
    "hemera-ajv": "^1.0.2",
    "nats": "^1.3.2",
    "nats-hemera": "^7.0.2"
    Richard Scappaticci
    @Richard-Scap
    import Hemera from 'nats-hemera';
    import hemeraAjv from 'hemera-ajv';
    import * as NATS from './dependencies/nats';
    
    // RPC dependencies
    export const nats = NATS.connection;
    const hemera = new Hemera(nats, { logLevel: HEMERA_LOG_LEVEL || 'info' });
    hemera.use(hemeraAjv);
    
    hemera.addSchema({
      $id: 'getQuoteRequestSchema',
      type: 'object',
      required: [
        'source_currency',
        'destination_currency',
        'source_amount'
      ],
      properties: {
        source_currency: { type: 'string', maxLength: 3 },
        destination_currency: { type: 'string', maxLength: 3 },
        source_amount: { type: ['string', 'number'] }
      },
      additionalProperties: false
    });
    Error: TypeError: hemera.addSchema is not a function
    Richard Scappaticci
    @Richard-Scap
    We resolved our issue. We needed to call hemera.ready() prior to hemera.addSchema(). We will likely open a PR to update the hemera-ajv docs to reflect this
    David
    @DavidBernal
    Hi, any plan to support typescript?
    Tyler Oliver
    @Tyler8oliver
    Can't figure out the best way to do this, but i am attempting to call a hemera service from a java service. What is he expected payload / subject needed to get my message received by hemera?
    veeramarni
    @veeramarni
    hemera-zipkin missing in latest packages, any reason to drop it?
    domdom8
    @domdom8
    hi guys, any NATS for .Net ?
    as hemera for Node.js