Spring Framework: The Foundation for Java Enterprise Apps
/spring-framework
Spring Framework is the dependency-injection container most enterprise Java still runs on, directly or under Spring Boot. It's unopinionated by design: you wire beans yourself instead of inheriting one framework's idea of a controller, which helps on large, custom systems but slows a newcomer reading someone else's config. Worth learning if you write Java for a living. Overkill for a small service where Spring Boot's defaults already do the job.
What is Spring Framework?
spring-framework is a Java framework that provides the plumbing enterprise applications need beyond core Java: dependency injection through an IoC container, AOP for cross-cutting concerns like logging and transactions, and infrastructure for Spring MVC web apps. It's the foundation the wider Spring project family - including Spring Boot - is built on top of, configured through Java config, annotations, or XML.
Core features and modules
- ✓IoC container that manages object creation and wiring through dependency injection, so classes declare what they need instead of constructing collaborators themselves.
- ✓Aspect-oriented programming (AOP) support for cross-cutting concerns - logging, transactions, security - without scattering that code through every class.
- ✓Spring MVC for building web applications and REST APIs with the framework's own request-handling pattern.
- ✓Configuration via annotations, Java-based config classes, or XML - pick whichever style fits an existing codebase.
- ✓Foundation layer underneath the wider Spring project family, including Spring Boot, Spring Data, and Spring Security.
- ✓JavaBeans-based bean lifecycle management, so components are created, wired, and destroyed by the container instead of by hand.
What you can build with Spring
- •Enterprise back-end services that need transaction management and dependency injection wired in from day one.
- •REST APIs and web applications built with Spring MVC.
- •Large Java codebases where teams want to swap an implementation (a database, a mail sender) without touching the classes that use it.
- •The base layer under a Spring Boot app - anything Boot auto-configures is still Spring Framework doing the work underneath.
Adding Spring Framework to your project
The README itself doesn't include a copy-paste dependency snippet - it points to the 'Spring Framework Artifacts' wiki page for binaries and a distribution zip instead. In practice, Java developers add Spring Framework as a Maven or Gradle dependency, or get it transitively through Spring Boot's starters, rather than downloading jars by hand. If you want to build the framework itself from source, the repo's Build from Source wiki page and CONTRIBUTING.md cover that path.
Why developers choose Spring
- ✓Unopinionated core - you're not locked into one way of structuring an app, unlike frameworks that dictate folder layout and conventions.
- ✓AOP and the IoC container solve cross-cutting concerns (logging, transactions) once, instead of duplicating that logic in every service class.
- ✓Backs the entire Spring project family, so skills transfer directly to Spring Boot, Spring Data, and Spring Security.
- ✓Apache-2.0 licensed, so there's no ambiguity about using it in a commercial product.
- ✓The wider documentation set - reference docs, a Javadoc API reference, and wiki pages - is maintained across Spring's sites, not just dumped in this repo's README.
Things to consider before adopting Spring
- △That same unopinionated design means more setup decisions land on you - XML vs. Java config vs. annotations is a real choice a new project has to make, not a solved default.
- △The README documents almost nothing about the framework itself - no quickstart, no code sample - so a first-time reader has to leave the repo (reference docs, spring.io/guides) before writing a line of Spring code.
- △Most teams now reach for Spring Boot's auto-configuration rather than wiring Spring Framework by hand, so the raw framework is increasingly something you inherit under Boot rather than choose directly.
Alternatives to Spring Framework
Frequently asked questions
Spring Framework is free for commercial use under the Apache-2.0 license, which allows using, modifying, and redistributing it in commercial products without paying any licensing fee. There's no paid tier, subscription, or separate enterprise license gate on the framework itself.
Spring Framework is the underlying IoC container and infrastructure (dependency injection, AOP, MVC); Spring Boot is built on top of it and adds auto-configuration and opinionated defaults so you write less setup code. Every Spring Boot app runs Spring Framework underneath - Boot doesn't replace it, it configures it for you.
Spring Framework is a Java framework, and its GitHub repository lists Java as the primary language. Because it runs on the JVM, other JVM languages like Kotlin and Groovy can use it too, though the framework itself is written and documented primarily for Java.
Spring Framework has a long track record as the base layer of enterprise Java applications and maintains published reference documentation, an API/Javadoc reference, and GitHub Actions CI builds defined in the repository. It's licensed under Apache-2.0 and governed by a public Code of Conduct, which points to an actively maintained project rather than an experimental one.
Spring Framework's core modules cover dependency injection through the IoC container, aspect-oriented programming (AOP) for cross-cutting concerns, and Spring MVC for web applications, tied together with JavaBeans-based configuration. The framework itself is the foundation; separate Spring projects like Spring Data and Spring Security add modules on top of it.
Spring Framework can be used without Spring Boot - it predates Boot and works standalone, configured through XML, Java config classes, or annotations with no auto-configuration involved. Spring Boot is a convenience layer on top, not a requirement for running Spring Framework itself.
The problem it solves
Java's language and standard library don't give you dependency injection, transaction management, or a way to swap an implementation (a database, a mail client) without changing every class that calls it - you either hand-wire that plumbing yourself or pull in a container that does it for you. Before frameworks like this existed, enterprise Java shops solved wiring and cross-cutting concerns (logging, security, transactions) with hand-rolled factory code or heavyweight EJB containers; Spring Framework became the lighter alternative that turned those problems into configuration instead of boilerplate.
How to use
This repository is the framework's source, not a getting-started tutorial - the README skips a code sample entirely and links out to the published reference documentation and to spring.io/guides for actual walkthroughs. Once it's on your classpath, the usual shape is: define beans via annotations or Java config, let the IoC container wire them together, and layer in Spring MVC controllers or AOP aspects only where you need them. For anything past 'how do I add a bean,' the reference docs are the real usage manual, not this repo.
Who should try it — and who should skip
Spring Framework is worth the learning curve for backend Java developers building enterprise systems, REST APIs, or anything that needs transaction management and swappable components across a large codebase - teams already committed to the JVM get the most out of it. Skip it if you're starting a small service from zero and don't want to make config decisions by hand: start with Spring Boot's defaults instead, or look at Quarkus/Micronaut if fast container startup matters more than the size of Spring's ecosystem. It's also not the right pick outside the JVM - there's no version of this for a Python or Node stack.
Related repositories
Want a second opinion on spring-framework?
Ask an AI that can read this page — one click and you get its take on spring-framework.