Definitely, especially in case of monolithic applications, the startup code needs to be modularized. Installers are a very good approach — then your main() method just calls them. I’d still opt for explicitly specifying the order in which they should be run.

So I think this can be implemented quite easily using e.g. a simple list holding a number of Installer instances, without the need for an IoC container :)

(by the way: you could probably argue that a well written monolith is in fact a number of microservices deployed together, communicating in-process instead of over HTTP)

Software engineer, Functional Programming and Scala enthusiast, SoftwareMill co-founder

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store