@cedric There's about 150 integrations, each built into its own application, currently they are all using Spring + Spring AMQP.
The DI is typically only one service being injected into one or two classes - feels like a waste.
I'm sure we can get the same effect using an interface and simply instantiating one instance as a static instance.
Integrations you typically can't unit test, so unless I'm missing something, DI seems like an unnecessary dependency here.