Joe, Yes, I believe one could build microservices which "federate" using PubSubHubbub by subscribing to one another.
Security is baked in the protocol with signed content delivery (and the use of HTTPS). Retries are considered good practices (but not part of the spec). I would argue that the most significant 'gotcha' is the use of HTTP which is a great protocol for widely distributed architecture, but not necessarily the best to deal with high frequency messages (lots of overhead). thanks -- *Got a blog? Make following it simple: https://www.subtome.com/ <https://www.subtome.com/>* Julien Genestoux, http://twitter.com/julien51 +1 (415) 830 6574 +33 (0)9 70 44 76 29 On Mon, Mar 16, 2015 at 10:25 PM, Joe Campbell <[email protected]> wrote: > Recently there's a trend to build an application using Microservices which > place an emphasis on small processes. There's also a move away from from > using an enterprise bus - instead preferring communication over > open/standard protocols. This makes sense but I find myself wishing for a > mechanism that publishes events [from one service to another] over http. > > Could hubbub be used for pub-sub between two microservices that expose a > restful (even odata) api? Is there any support for security, retries, > circuit-breakers etc? > > Or would this lead to a yet another bloated middleware product? > > Joe > > -- > > --- > You received this message because you are subscribed to the Google Groups > "Pubsubhubbub" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "Pubsubhubbub" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
