Software Architecture - Why do we use Layered Architectures?

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 :

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:

image info

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:

image info

Implementing The Web Layer

Earlier, the web layer of a Java EE application is responsible for rendering the final view to the user with technologies like JSPs and variety of templating languages. With the advent of RESTful web services and evolution of JavaScript SPA frameworks, this has changed drastically.

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.

image info

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

image info

Lets look at the important business layer responsibilities:

Transaction Management

This is taken care of by Java Transaction API (JTA) and Spring Transactions.

Implementing The Access Layer

image info

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.

Other Layers

image info

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

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:

image info


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.

Related Posts

Design Patterns For Beginners - with Java Examples

In this guide, we give you an introduction to the world of design patterns.For each pattern, we understand 1) the pattern a2) the context in which it is applicable - with a real-world example.

Software Design - Encapsulation - with examples

Encapsulation is one of the important goals of Software Design. What is Encapsulation? Why is it important? Let's get started.

Software Design - How do you keep your design simple?

With extreme programming and agile, the focus is being lean and keeping your design simple. In this context, how do you ensure that your design remains good and evolves along with the application requirements? Here are a five tips you can focus on.

Software Design - What is Abstraction?

Abstraction is one of the fundamental concepts of software engineering. It is all about hiding complexity while building your application.

Software Design - Cohesion - with examples

High Cohesion is one of the important aims when your architect and design your software. What is it all about?

Software Design - Coupling - with examples

Software architects and programmers love low coupling. What is coupling? Why is coupling important? Let's get started.

Software Design - Introduction to Evolutionary Design

With extreme programming and agile, the focus is being lean and doing just in time design. In this context, how do you ensure that your design remains good and evolves along with the application requirements?

Software Design - Five Things To Look Out For In A Design Review

Doing a software design review is never a straightforward task, with a number of things to look out for. In this short article, we look at five such aspects, which will help you structure your review process in a better way.

5 Qualities of a Great Software Architect

In this article, we look at some of the important qualities of a great software architect. While we focus on application architects, most of these are applicable for enterprise architects as well.

5 Important Responsibilities of a Software Architect

In this article, we look at some of the important responsibilities that an architect is expected to handle. Although we chiefly focus on application architects, most of these also hold true for enterprise architects as well.