shlomiassaf / pebula-node Goto Github PK

I stumbled upon the SbServer implementation, which is awesome to work with microservices! But it looks like it is not documented...

@pebula/nesbus works for us with Nest.js@8 (installed through --force switch). I'm not sure how to create PR, because tests fail on empty repository (Connection string malformed: each part of the connection string must have an = assignment.). I provided undocumented SERVICEBUS_CONNECTION_STRING env variable.

Hello,

I am unable to insert a string fetched from env into Queue name either through config service, process.env.QUEUE_NAME or through a util function returning queue string. Also this is not accessible either.

@Queue<MethodDecorator>({
    name: 'queue.name',
    // want to to do one of following. 
    //name: new ConfigService().get('AZURE_SERVICE_BUS_QUEUE'),
    // name: process.env.AZURE_SERVICE_BUS_QUEUE,
    // name: serviceBusQueueString(),

    receiveMode: ReceiveMode.peekLock,
    handlerOptions: {
      autoComplete: false,
    },
  })
  async myQueueEntity(@Ctx() context: SbContext): Promise<void> { //... 
}

Docs state:

The reactive handler pattern works great with the @nestjs/cqrs module 
and in general most of the event driven designs out there. You can easily 
implement event sourcing with it.

Would it be possible to provide an example?

@pebula/nesbus conflicts when azure service is upgraded to v7. I'm unable to get the nestjs running when azure service bus is upgraded to latest version. On v1 the app works fine with @pebula/nesbus.

Can you please update @pebula/nesbus to work with latest version of azure service bus?

Hi,

I noticed a little type declaration problem for the SbResourceGroup class. My Typescript compiler is not happy with this =D ! I just installed the package and launched my app.

This does the trick :

Hello,

I want to write a Message Consumer that will continuously be listening for incoming messages from a defined Topic of Azure Service Bus.

Can you let me know which methods i have to use from your library. Its not clearly mentioned the documentation.

Can this Message Consumer be embedded into existing NestJS MicroService or do i need to create a separate NestJS application.

Hi @shlomiassaf, I'm using this code within a controller

  @Subscription<MethodDecorator>({
    name: 'my-subscription',
    receiveMode: ReceiveMode.peekLock,
    topicName: 'my-topic',
    handlerOptions: {
      autoComplete: false,
      maxConcurrentCalls: 1,
    },
  })
  async topicUpdates(@Ctx() context: SbContext) {
    console.log(context.getData());
  }

I receive the message, but it is still removed from the topic subscription, even though I am using autoComplete: false and never call context.getMessage().complete()
Trying to understand why this might be happening. Thanks.