Suggestion: Separate UI and API

[john-goldsmith]

I noticed that the contents of the kafka-rest repo are duplicated in this repo. I imagine that keeping those in sync would be challenging, so I'd suggest ripping that out of this repo in favor of some environment/configuration values that tell React to talk to the API at a particular host/port.

Case in point: See kafka-rest #1 -- the Docker change would need to be propagated to this repo as well.

[krystianity]

Hi @john-goldsmith thanks for the interest and opening an issue here.
We are discontinuing the kafka-rest-ui and kafka-rest, as clones of the JVM versions.
We just dont think the architecture behind them is solving its purpose. (Spinning up consumers and seeking offsets, just takes too long).

We will however ship a new solution soon, that works with an additional backend to offer immediate response times, without spawning seeking consumers.