3 ms·
Yes. At the BBC project I've talked about before (µservices to monolith, 100x - 1000x faster), I also removed all external configuration files. This turned out
by mpweiher 11y ago
Yes. At the BBC project I've talked about before (µservices to monolith, 100x - 1000x faster), I also removed all external configuration files. This turned out great, and it made "deployment" as trivial as possible. Copy jar file to directory, start (maybe with a command line argument, don't remember 100%).
Why no config files? Very simple: a change to config file was just as "expensive" in terms of deployment as a code change, so around a day overhead. Compared to that overhead, the recompile was not measurable, so there was no benefit to config files.
On the other hand, apart from making everything simpler, configurations could now be coded as Java classes, with all the subclassing/abstraction/composition goodness.
- tokenizerrr 11y agoThe way I like to do things is mostly as you describe, but also to set up the configuration to be (de)serializable by your favorite xml library. The defaults are in the code, but they can be overridden on a per-deployment basis.