There is always a time when you go too far and a time when you don't get far enough. If you can, you refactor when it becomes clear. In the case of Spring thou

There is always a time when you go too far and a time when you don't get far enough. If you can, you refactor when it becomes clear. In the case of Spring though, they have a tough problem to solve. They are gluing technologies together, so they are always going to have factories of factories, adapter of adapter, and that kind of things. And if in the bunch of tech they glue there is an outlier that behaves unlike the other, or a poorly designed one, they will need to handle it somehow. Another feature that weights on Spring design is that almost the whole framework is public. Generally you would have a core architecture and well defined key extension points. Not with Spring, and that means more "useless" abstraction and therefore more mess.