On Mon, Apr 25, 2016 at 7:58 PM, Bill Farner <wfar...@apache.org> wrote:
> I don't have a firm example in mind, I just don't think the approach > recommended by Zameer is optimal. It's only marginally better than forking > (and probably requires you to fork for the sake of sanity). > > Thinking out loud, it would be nice if Kafka had a JMS interface/bridge, as > it would allow us to add support for a bunch of backends with one > implementation. Unfortunately that does not appear to be the case. > That said - supporting a JMS interface doesn't sound too bad on the aurora end. Motivated consumers could write a bridge presumably if they insist on using Kafka. > On Monday, April 25, 2016, Dmitriy Shirchenko <cald...@gmail.com> wrote: > > > @wfarner > > > > Can you help me out and clarify what you mean by 'First-class mechanism'? > > An example would be awesome. > > > > On Mon, Apr 25, 2016 at 4:40 PM Dmitriy Shirchenko <cald...@gmail.com > > <javascript:;>> > > wrote: > > > > > Has anyone built something that can subscribe to events and then send > > them > > > to a pub/sub system? Maybe can give pointers on how you would approach > > this? > > > > > > Our use case is sending TaskStateChange`s into an internal Kafka topic. > > > > > > Thanks! > > > > > >
