Classes which run topologies often repeat the same code and pattern to:
- populate the configuration from a file instead of ~/.storm
- determine whether to run locally or remotely
- set a TTL for a topology
Flux provides an elegant way of dealing with these but sometimes it is simpler to define a topology in Java code.
In StormCrawler, we implemented an abstract class named ConfigurableTopology which can be extended and saves users the hassle of having to write code for the things above. I will open a PR containing this class so that we can discuss and comment whether it is of any use at all.