In this article, we explore the reasons why we build applications with several layers. We also look at different options for each layer in the Java world.
You will Learn
- Why Have Multiple Layers?
- What are typical layers and their responsiblities?
- What are the typical frameworks used in each layer in the Java world?
This is the fifth article in the following series of articles on Software Architecture :
- 1 - Quick Introduction To Software Architecture
- 2 - What Is The Goal Of a Software Architect?
- 3 - 5 Qualities of a Great Software Architect
- 4 - 5 Important Responsibilities of a Software Architect
- 5 - Software Architecture - Why do we use Layered Architectures?
Why Have Multiple Layers?
When we build any large application, such as a web application or service, we try to organize it into multiple layers. We could go for layers such as Web, Business, Access, among others:
The reason we go to such lengths is a very important underlying principle : separation of concerns.
Each of the layers above have different responsibilities. Web layer is responsible for presenting information to the user. The Business layer is responsible for application’s business logic. The Data layer is responsible for taking care of the data access, and configuring and talking to the data stores. You might also have an additional access layer to talk to external applications, or queueing messages for dispatch.
By defining each layer to have a separate responsibility, you ensure high cohesion with-in each such layer.
Layers In Enterprise Java
When it comes to the Java world, the typical organization of enterprise applications follows this schematic:
Implementing The Web Layer
Today, we expose a REST API from the Java Web layer, and a front-end framework (such as AngularJS or ReactJS) handles the user presentation.
The main responsibility of a web layer is to talk to business layer and send a proper response to REST API calls.
Another responsibility that a web layer typically handles is authentication and authorizations using a module like Spring Security.
A few important decisions when designing your web layer are
- Should the application have state? If yes, you need to store session information about the user. Ideally, you should not.
- Which framework to use? The popular options are Spring Boot (MVC), JAX-RS(REST), JAX-WS(SOAP).
Implementing The Business Layer
Lets look at the important business layer responsibilities:
This is taken care of by Java Transaction API (JTA) and Spring Transactions.
Implementing The Access Layer
The following are the responsibilities of the Access layer:
Communicating with Data Store
If your application communicates with an external database, JPA might be a good choice. If very complex database queries are needed, then you might want to use JDBC or MyBatis.
Spring Data JPA might be a good starting point for using JPA and Hibernate.
Communication With External Interfaces
This layer provides interface with the JMS module. It also communicates with AMQP implementations.
One of the most important aspects that needs to be handled in any system is Cross Cutting Concerns. This includes tasks such as logging, performance and security.
Typically these are implemented using Aspect Oriented Programming. AspectJ and Spring AOP are options to consider.
Unit testing of the application is another important concern. Typical frameworks that are provided include JUnit, Mockito and Spring Unit.
Do check out our video on this:
In this article, we understood why we need to have multiple layers in an application. We looked at the layers in a typical Java web application, along with framework options available. We then had a look at the makeup of the individual Data, Business and Access layers of a typical Java web application.