Well I wouldn't use Spring, so that solves a lot of the problems... :) I was never really a fan of DI. Part of my point is your application should be fast eno

Well I wouldn't use Spring, so that solves a lot of the problems... :) I was never really a fan of DI. Part of my point is your application should be fast enough before the JIT kicks in. Ideally, you should also do performance testing. Incorporating that with your release go or no go is a great approach, IMO, if you do releases very often.