Production

[henry-hz]

Hi @gfiehler , nice plugin ! thanks for sharing.
are you using in production ? who much rabbithub is different from resthooks.org guidelines ?

[gfiehler]

Hi Henry,  Thanks for the interest in this project.  You may already know this, but to make sure we are talking about the same thing, this project is a management UI for RabbitHub, which is a separate project.  The Rabbithub project has been around for a while and the current master is owned by Brett C.  here .  brc859844/rabbithub | | | | | | | | | | | brc859844/rabbithub rabbithub - Experimental RabbitMQ PubSubHubBub interface | | | | I am working with Brett to get the updates I have made here gfiehler/rabbithub | | | | | | | | | | | gfiehler/rabbithub rabbithub - Experimental RabbitMQ PubSubHubBub interface | | | | The management project only works with my updated copy.  I hope to get Brett my pull request by the end of the year.  Brett has used the current master in production and others have as well.  We are not in production yet, with the latest updates on my forked copy.  We are in QA at this time.  I have tested on a 3 node cluster on medium size VMs and was able to get to 1000 tps with no issues at all.   My company is moving from a current activemq in house webhooks framework to rabbitmq and my latest updates to Rabbithub, I built the management plugin for our convenience, but you can do everything via apis.  We are finalizing our Rabbitmq infrastructure and plan to start migrating applications to this system next year in production.  As well as all new webhook integrations will go through Rabbithub as well. Thanks for the link to resthooks, in all my google searches while looking for a solution a year ago, I had never seen this before.  It is well done.  The original Rabbithub was written by Tony G and it was based on PubSubHubBub spec so it has many similarities.  I did a quick read through of the Resthooks docs and I believe we are pretty much in line.  The only major missing component is RabbitHub does not currently store a parent or account relationship with the subscriber.  But that would be an easy addition, I need to see if I can find an example of what people are storing for this.  Here are some of there areas and how Rabbithub addresses it in <...>  - Mechanism to store subscriptions <yes, but currently no account information on the subscriber> - Mechanism to modify subscriptions via API <yes> - List and implement event types <implement, but no list, in rabbitmq events are really exchanges and queues and you can get these via rabbitmq management apis> - Mechanism to send hooks <yes> - An event name or names the subscription includes <yes you can subscribe to one queue or exchange per subscription, however, muliple subscriptions can have the same callback url> - A parent user or account relationship <not at this time> - A target URL to send the payloads <yes, referred to as callback url> - (optional) Active vs. inactive state <yes, added in latest updates> Please see list of api's available on the readme page of https://github.com/gfiehler/rabbithub/tree/3.6.3-Feature-Updates2 If the subscriber callback returns a 400 or above the message is returned to the queue and will either be retried or sent to a dead letter exchange via rabbitmq config.  We do this and have a separate dead letter error manager that does the retries with configurable delays and numbers of retries.  This project is not a plugin and is not currently being planned for open source as it has some very proprietary features at this point.  But is a standard component to create when using rabbitmq and I could not find any current open source projects for this area. For security the original supported basic auth with rabbitmq configured username/password for api call.  I have just added the ability to use basic auth when calling the target or callback url.  This should be on Github soon.  The original, following the PubSubHubbub spec does the identity confirmation where Rabbithub sends a token to the subscriber to confirm. If you read the readme listed above it shows all the features of Rabbithub in that version.  I am finalizing the last update before my pull request, so if there is something you would like to see, if time permits, I would be happy to look into adding it. FYI we primarily use this for internal use, we do not have it open to the public to subscribe, our clients are applications within our corporate portfolio, however, many of these are cloud based applications. sorry fo the long winded response, but I hope this answers your questions.  As stated I am doing some current updates before my pull request this year, then I will be looking at some updates next year and always happy to get ideas or help in the process. Gregg  On Friday, December 16, 2016 2:52 AM, Henry Hazan <[email protected]> wrote: Hi @gfiehler , nice plugin ! thanks for sharing. are you using in production ? who much rabbithub is different from resthooks.org guidelines ?— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[henry-hz]

Thanks for the detailed (and amazing) response. Today we integrate with ERPs using standard POST requests. I hope to move soon to rabbitmq, rabbithub and your plugin rabbithub_management. I update you with issues when we start :)
I am contributing to this https://github.com/slashdotdash/commanded lib for our CQRS/ES backend, it may interest you also.
best regards
Henry

[gfiehler]

Hi Henry, wanted to give you a quick update.  We just upgraded to Rabbitmq3.6.6 and it was a change that effects rabbithub, Rabbit decided to change the definition of Queue.  I have it working but it will take me a week or so to get it packaged.  This is an updated version that I will be putting up onto Github with versions for 3.6.3 and 3.6.6.  I have added basic auth for outbound calls to subscriber and ability to configure contact information for the subscriber and few other little items. Gregg On Saturday, December 17, 2016 3:35 PM, Henry Hazan <[email protected]> wrote: Thanks for the detailed (and amazing) response. Today we integrate with ERPs using standard POST requests. I hope to move soon to rabbitmq, rabbithub and your plugin rabbithub_management. I update you with issues when we start :) I am contributing to this https://github.com/slashdotdash/commanded lib for our CQRS/ES backend, it may interest you also. best regards Henry— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[henry-hz]

Ok Gregg! Thanks for the follow up Best regards Henry

…

On Fri, 20 Jan 2017 at 23:36 Gregg Fiehler ***@***.***> wrote: Hi Henry, wanted to give you a quick update. We just upgraded to Rabbitmq3.6.6 and it was a change that effects rabbithub, Rabbit decided to change the definition of Queue. I have it working but it will take me a week or so to get it packaged. This is an updated version that I will be putting up onto Github with versions for 3.6.3 and 3.6.6. I have added basic auth for outbound calls to subscriber and ability to configure contact information for the subscriber and few other little items. Gregg On Saturday, December 17, 2016 3:35 PM, Henry Hazan < ***@***.***> wrote: Thanks for the detailed (and amazing) response. Today we integrate with ERPs using standard POST requests. I hope to move soon to rabbitmq, rabbithub and your plugin rabbithub_management. I update you with issues when we start :) I am contributing to this https://github.com/slashdotdash/commanded lib for our CQRS/ES backend, it may interest you also. best regards Henry— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA9pWGVH3UrYw0HSf7zYXYZYZbW-yl6Iks5rUSjfgaJpZM4LPA_e> .