Would be better UX than just emphasizing the dependencies in the README

Check existing properties files and data folders to see what files already exist and display them as "inactive" brokers that can be spun up

• Would need to make sure an inactive broker has both corresponding properties file and data folder via the ID

If for some reason a user starts up a broker outside of the web client, they should be able to make a new GET request to the backend to update the broker list in the client.

I.e. check if the folder passed in for properties files also has additional server.properties files, if not throw error message to the front end

Kafka installed on MacOS with homebrew seems to automatically install a zkServer.sh script that can be used to check if the Zookeeper server is online, but no equivalent file is included with Windows installation.

What is the equivalent in Spring?

• Force killing a broker causes Zookeeper to throw an error later because the ephemeral node connection was not properly shut down, as described here and here.

• Find the programmatic equivalent of pressing Ctrl + C in a terminal window

Kafka's native Admin API does not support topic deletion on Windows machine. two options:

1. wait until Kafka supports the feature for Windows
2. manually delete log folder if it can be done safely without any side effects