This document summarizes a presentation given at the 4th TCS Iberoamerica Technical Architect's Conference 2009 about the benefits of using design patterns with the Spring Framework in J2EE applications. The author, Oscar Israel Ramírez Vital, argues that traditional J2EE applications often lacked design patterns and were repetitive and difficult to maintain, while the Spring Framework incorporates best practices design patterns and allows developers to focus on business requirements rather than framework details. Through a comparison of pure J2EE and Spring-based J2EE applications, the author demonstrates that the Spring Framework can reduce development time by over 30% and improve application server performance by over 20%. The author concludes that simplicity, as provided by the Spring Framework,

1. The 4th TCS Iberoamerica Technical Architect's Conference 2009
The profit in the effective use of design patterns with Spring
Framework within J2EE applications
Author Oscar Israel Ramírez Vital
Affiliation TCS’s Employee
Address Hacienda Chintepec No 110-18
Fracc. El Jacal, C.P. 76180,
Corregidora, Querétaro,
Phone (442) 222 90 95
Email: oscar.ramirez@tcs.com
Motivation:
Today, in the current complex and large-scale enterprise scenarios, the companies need
smartest enterprise solutions for resolve the request of the customers, markets, trends
and government. In this context Java offers one of the most robust software
specification in enterprise environments, J2EE (Java 2 Enterprise Edition), gave to the
developers the option of build applications in heterogeneous systems with the famous
legend “write once, run anywhere”. The Java platform offers serious advantages, for
example the possibility of integrate with legacy systems, but the reality isn’t only
happiness. The monolithic J2EE specifications, like those adopted by the development
community in the early days, didn't help to reduce the quantity of code required for the
development team, in this scenario, the developers fell in the temptation of the build
components without any design patterns, explain the complex specification like excuse.
By the way, in the actually the Java developers don’t use frameworks because some of
them are over complex and require you to write reams of repetitive code, it should be an
immediate big red flag, an the question is: Why did we have to write so much repetitive
boilerplate code?. The consequences of this are poor and repetitive code and
applications with lowest quality levels, finally this situation impacts in the maintenance
process costs for application fail over and the make more complex of understand the
application for the development team.
Spring Framework is an open source framework for the application development in Java
platform. Spring use a variety of some of the best design patterns for the development
applications and the developer only must use it for the development tasks. The
developer don’t should know the artifacts and the “know how” of the framework layers,
he can concentrate in business requirements.
Certainly, working with Spring feels a lot better than traditional J2EE approaches,
because to save time and effort for the developer, and make that the application works
over built framework component’s under some of the best design patterns for J2EE.

2. The 4th TCS Iberoamerica Technical Architect's Conference 2009
Approach:
Throught the comparison between a pure J2EE application and J2EE application built
with Spring Framework, I can demonstrate the profit in cost, time and effort for the use
of Spring Framework in Java development environments.
Results
• Spring Framework reduces the development time in more of 30%
• The J2EE application can improve the Application Server performance in more
of 20%.
Conclusions
In the end, simplicity often wins the day.
Keywords: J2EE, Spring Framework, Design Patterns, Profit