Depends on the enterprise. We don’t use it and we’re pretty big. Many other teams here don’t, either. Some do — it’s a big place. I suspect a lot of enterprise

Depends on the enterprise. We don’t use it and we’re pretty big. Many other teams here don’t, either. Some do — it’s a big place. I suspect a lot of enterprise devs inherit the decision, or move from project to project and don’t want to reinvent the wheel, and want a framework that’s portable (ie take their skills to another company), can hire for, etc. We don’t because managing our dependencies is important for us. Also we have a long-lived “product” codebase so keeping it simple pays off. Concrete advantages for us: Faster startup, smaller footprint, easier to reason about dependencies, and also the code is simpler, even for new joiners — anyone with a decent knowledge of Java will pick it up quickly. It doesn’t tick the “has worked on Spring” checkbox but it’s not like it’s made us unemployable. People do leave from time to time.