GithubHelp home page GithubHelp logo

Comments (6)

raqbit avatar raqbit commented on July 24, 2024 1

Ideally, Watermill's amqp.NewSubscriber method would automatically reuse a single connection, creating instead a new Channel

The same could apply to publishers as well. For instance I'm working on a "processor" of sorts which acts on messages in one queue and outputs new messages to an output queue via a publisher. Currently watermill would create two connections, one for the subscriber and one for the publisher.

If this isn't feasible, please consider adding a new method that accepts an existing *amqp.Connection parameter (vs the current amqp.Config param.)

In this case you'd lose all benefits of having watermill take care of connection management for you. I think it'd be better if watermill somehow exposed the internal connection manager and allowed us to re-use that instead.

Another thing I noticed while looking at watermill's AMQP package is that an AMQP channel is created for each publish, which also isn't recommended. (Citation.)

In an ideal world the AMQP connection should be created once (unless you need multiple configs), the subscriber channel should be created once (per subscriber) & be long-lived and the same goes for the publisher channel.

from watermill.

roblaszczak avatar roblaszczak commented on July 24, 2024 1

Hello, I will be happy to merge any changes that are working and not affecting current functionality and flexibility :)

Feel free to experiment, with current tests It should be pretty simple. If you need any help, please hit me on Gophers slack so I can help. To make it easier, I shared some tribal knowledge about how I do debugging of the tests here: https://watermill.io/docs/troubleshooting/#debugging-pub-sub-tests

from watermill.

bstasyszyn avatar bstasyszyn commented on July 24, 2024 1

I have a pull request open that (hopefully) resolves this issue: ThreeDotsLabs/watermill-amqp#9. Please review. Thx! @roblaszczak @ferbs @jawr @raqbit

from watermill.

jawr avatar jawr commented on July 24, 2024

An extension of this would mean we could remove/stop router handlers dynamically. At the moment the Handler shutdown process attempts to close the subscriber, which if shared would be undesired.

from watermill.

ferbs avatar ferbs commented on July 24, 2024

@bstasyszyn I've switched off the project using watermill-amqp so will go silent (leaving this issue open.)

from watermill.

bstasyszyn avatar bstasyszyn commented on July 24, 2024

PR was merged: ThreeDotsLabs/watermill-amqp#9. This issue can be closed.

from watermill.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.