Where should Iggy demo apps live?

[justinmclean]

Hi,

I've been playing with an Iggy demo. It shows changes in real time, and what happens when you push more messages than a consumer can read.

There are two options were we can put it:

In apache/iggy, alongside the existing examples.
In a new apache/iggy-demos repo, with a folder per demo. Anyone could submit a demo app or a use case there.
A separate repo keeps apache/iggy smaller and gives the community one place to share what they build. Keeping demos in apache/iggy means they are built and tested against the current code, so I think the second option is best.

What do people think?

Kind regards,
Justin

[hubcio]

hi,
i vote for apache/iggy-demos purely because our CI in apache/iggy is already overloaded.i dont see a reason why we should keep it in main repository, demos should just work against stable version of iggy.

[justinmclean]

Thanks @hubcio. The repo is now at https://github.com/apache/iggy-demos, starting with the Kafka producer/consumer client and demos. New demos and use case submissions go there.