How a Group of Developers Took Back Control from Enterprise Java Spring: The Documentary (Category Software)

I watched it this weekend. spring-documentary. I love technology movies, which show not only what happened, but how much pain technology was trying to alleviate. Spring’s story is especially good: it’s not just a story about the popular Java framework, but a story about how developers got tired of the heavy enterprise model and began to regain control of the code.

In the beginning 2000Enterprise Java looked very solid: specifications, application servers, EJB, XML descriptors, containers, large vendors. It was as if it were “adult-like.” But for conventional development, it often meant a slow feedback loop, complex testing, and a sense that simple business logic suddenly requires too much infrastructure magic.

Spring emerged as a response to this friction. Rod Johnson first formulated a critique of the then-J2EE approach in a book.Expert One-on-One J2EE Design and Development", and the code from the appendix to the book gradually turned into Spring. I like that the alternative came not as another big specification from the top, but as a practical set of engineering principles from the bottom: POJO instead of heavy components, Dependency injection and Inversion of Control instead of a rigid bind to the container. Testability is a normal design requirement. Composition of objects instead of feeling that the real architecture must be hidden in the application server. Essentially, Spring told developers: Business logic can be regular Java code again. It can be read, replaced with dependencies, tested separately and gradually integrated into a larger system. It sounds almost corny today, but there was a strong architectural shift back then.

It is interesting that Spring did not stop at the first victory. Over time, it became a large ecosystem, with its own configuration, conventions and complexity. The next step was Spring Boot: less manual setup, sensible defaults, embedded server, quick start of the application. Boot is well into the era of microservices, containers, and cloud-native development, where the old approach of assembling all the enterprise infrastructure around the application first has become too heavy again.

But there is a second side to this story. When technology wins, it becomes infrastructure. And the infrastructure is getting legacy, versions, upgrade cost, security patches, compatibility and long-term maintenance. Spring started out as a way to take back control of developers and is now part of a vast enterprise landscape that needs to be managed carefully. Funny that the main sponsor of this film is the company. HeroDevsIt saps the code of legacy applications that live on frameworks and libraries that have long since left the support cycle, but no one is ready to rewrite the business applications themselves. As a result, the guys from HeroDevs are engaged in such maintenance and fix mainly vulnerabilities in the old codebase.

For me, the big takeaway is that strong technologies often emerge not from a desire to “make another framework,” but from a desire to remove the friction between idea, code, test, and production. They win not only by features, but by changing the everyday experience of the developer.

#Software #Java #Spring #Architecture #Engineering #OpenSource #History