Architecture of Spring Framework - Modularity and Spring Modules


One of the most important features of the Spring framework is its modularity. It is not one big monolith framework. What is the architecture of Spring Framework? What are Spring Modules? How are they organized?

You will learn

  • What is the architecture of Spring Framework?
  • How is Spring Framework Modularized?
  • What are different Spring Modules?
  • Which modules provide which Spring Features like Dependency Injection and Auto wiring?
  • How can you develop applications with multiple layers with Spring?

Spring Framework

This is the fifth article in a series of articles on Spring Framework:

Spring Architecture and Modules

Let’s look at the modules that are present in a typical Spring Project. image info

It is not organized as one big JAR file. It is composed of a large number of smaller JAR files.

Spring is organized into modules. Here is how Spring is organized conceptually: image info

Container

This is the most heavily used part of the Spring framework. This includes modules such as:

  • Beans: To manage the application dependencies
  • Core
  • Context: To maintain the application context

Database Access And Integration

Spring provide excellent options for implementing data and integration layers.

The important data access modules are:

  • JDBC : To talk to relational database using JDBC
  • ORM : Provides good integration with all ORM (Object Relational Mapping) frameworks, such as Hibernate and MyBatis.
  • JMS : If you want to talk to another application over a queue, JMS provides an excellent option. Spring has good integration with JMS.
  • OXM : This module provides good integration in scenarios where object to XML mappings are required.
  • Transactions : Transaction management is an important part of data access integration functionality. Ideally, you want the transaction to be fully successful, or completely rolled back. If a transaction has 4 steps and failed at the third step, the previous two successful steps must also be rolled back. Spring has great support for transaction management.

Web

Spring has very good support to develop your web layer:

  • Spring MVC : It is Spring’s own web framework
  • Struts : Spring provides good integration with Struts.

Cross Cutting Features

An application is typically developed in multiple layers. For example, a web application is often designed to have three layers: web, business and data:

image info

There are many things that are applicable to more than one layer. Those are called cross cutting concerns.

Unit Testing

One important cross cutting concern is unit testing. We want to be able to unit test code in all the three layers mentioned above. Spring Test framework provides good support for unit testing.

AOP

AOP stands for Aspect oriented programming. This module is useful for implementing features such as security and logging. Spring AOP provides basic AOP features.

Spring provides good integration with the AspectJ framework to do advanced AOP.

Do check out our video on the same topic:

image info

Summary

In this article, we had a brief look at the modular structure of the Spring framework. It is not a single monolith, but is organized as a set of small modules.

Related Posts

Spring Boot Tutorials for Beginners

At in28Minutes, we are creating a number of tutorials with videos, articles & courses on Spring Boot for Beginners and Experienced Developers. This resources will help you learn and gain expertise at Spring Boot.

Introduction To Aspect Oriented Programming and Cross Cutting Concerns

Software applications are built in layers. There is common functionality that is sometimes needed across layers - logging, performance tracing etc. How do you implement these common features?

Programming Basics - Introduction To Object Oriented Programming

Object oriented programming (OOP) is all about thinking in terms of objects. Let's dig deeper.

Programming Basics - Five Things To Think About While Programming

You would obviously want to write code that meets your core requirements and provide good performance - choosing right data structures and algorithms to use is the fundamental part of programming. What are the other things that you need to worry about? Here are five things that we think are essential.

Asynchronous communication with queues and microservices - A perfect combination?

In this article, we throw some light on what asynchronous messaging is all about and discuss why you should consider it for your microservices architectures.

Microservice Best Practice - Build an Archetype

In this article, we focus on learning why creating proper archetypes is important for successful microservices architecture.

Microservice Architecture Best Practices - Messaging Queues

In this article, we discuss why Messaging queues are needed, and how they form the cornerstone of communication in microservices architectures.

Microservice Best Practice - Why do you build a Vertical Slice?

In this article, we look at what is a vertical slice, and why we build it. We also discuss the best practices involved in building vertical slices.

Microservices Architectures - Event Driven Approach

In this article, we talk about event driven approach, in the context of microservices architectures. We also discuss what are the advantages of using an event driven approach.

The 12 Factor App - Best Practices In Cloud Native Applications and Microservices

In order that an application be deployed in the cloud and enjoy features such as auto scaling, it first needs to be cloud native. In this article, we have a close look at the best practices for cloud native applications, popularly known as The 12 Factor App.