The Spring Framework is a programming and configuration model for Java applications, built around dependency injection (also called inversion of control) and aspect-oriented programming. The project describes itself as the foundation for all Spring projects, providing “everything required beyond the Java programming language for creating enterprise applications for a wide range of scenarios and architectures.” Its core idea is to let the framework handle the plumbing of enterprise software, such as object wiring, transactions, and resource management, so that teams can focus on business logic.
Spring grew out of Rod Johnson’s work in the early 2000s, particularly the sample code from his book on J2EE development, which argued that enterprise Java had become too heavy. At the time, the dominant pattern was Enterprise JavaBeans (EJB), which required developers to write against intrusive container APIs, deploy to expensive application servers, and tolerate slow build-and-test cycles. Spring offered an alternative: ordinary Java objects (POJOs) whose dependencies were supplied by a lightweight container, configured externally rather than hardcoded. The framework was released under the Apache License, with the first production 1.0 release arriving in 2004.
Dependency injection is the central mechanism. Instead of an object constructing or looking up the collaborators it needs, those collaborators are provided to it by the container, originally through XML configuration and later through annotations and Java configuration classes. This inversion makes components easier to test in isolation, easier to reconfigure, and less tightly coupled to specific implementations. Around this core, Spring layered portable abstractions for data access, transactions, messaging, and web development, so that application code did not have to bind directly to a particular database, server, or vendor API.
Over two decades Spring expanded into a broad ecosystem of projects covering data access, security, batch processing, messaging, and cloud-native development. The single most consequential addition was Spring Boot, which packages Spring applications with sensible defaults, auto-configuration, and an embedded web server, letting developers run a service with a single command and minimal boilerplate. Spring Boot’s convention-over-configuration approach made Spring the default choice for new Java services and microservices.
Spring’s influence reached well beyond its own codebase. By proving that a lightweight DI container could replace much of the heavyweight EJB stack, it pushed the broader Java platform toward simpler, annotation-driven, POJO-based programming models, ideas that were later absorbed into the standard Java EE and Jakarta EE specifications themselves. Today the framework remains one of the most widely used foundations for server-side Java, with the codebase actively maintained on GitHub and shipping major releases on a regular cadence.