Hey Jeremiah,

That’s a good question, and it ultimately will come down to what you need.

For instance, maybe you have an existing Dropwizard that you’d like to *also 
*consume messages in addition to whatever else it’s doing. Maybe having a 
http health check, and an admin page that’s familiar is beneficial. 

Spark streaming, and Samza (which sorry if this is wrong, not super 
familiar with it) would require you to set up a cluster, and maybe that’s 
not worth it in all cases, though I can definitely see them being useful 
pretty broadly.

Or maybe you’re just wanting to use the Kafka streams APIs (which granted, 
what I have now in dropwizard-Kafka doesn’t support), which again doesn’t 
require a cluster, but gives some of the features of spark streaming (and 
Samza?).

Just some thoughts, hopefully that clarifies.

On Tuesday, May 14, 2019 at 10:03:41 AM UTC-4, Jeremiah Adams wrote:
>
> Can you share a high overview of use cases you h ave for the kafka 
> consumers in dropwizard? We use dropwizard for our rest services,  and 
> apache samza for kafka stream processing. I am interested to see how you 
> are using kafka consumers in dropwizard.
>
>
>
> On Saturday, April 27, 2019 at 3:14:10 PM UTC-6, mza...@apple.com wrote:
>>
>> Hey dropwizard-dev,
>>
>> We've got some modules we'd like to open source that we use internally at 
>> Apple. Some of those might make sense to be included in the core Dropwizard 
>> project, but others definitely don't, and it would make much more sense to 
>> have them live outside of the Dropwizard repo. 
>>
>> We're hoping we might be able to contribute these to the Dropwizard 
>> organization (https://github.com/dropwizard) instead, as that seems like 
>> a place where it would make sense for Dropwizard extensions to live. 
>> However, we wanted to consult you guys to see if you had any strong 
>> preferences one way or another, or if there's any process we should be 
>> aware of in order to add a project to the Dropwizard GitHub organization.
>>
>> It might be worth mentioning that it would be easier for us to open 
>> source them if they can live in the Dropwizard organization, rather than a 
>> brand new spot, due to how our corporate open source policy works. 
>>
>> Thanks!  
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"dropwizard-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dropwizard-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dropwizard-dev/10055c53-c2b9-48ed-9f5a-ef75c863ea9f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to