Software Design - Separation Of Concerns - with examples

Software architects and programmers love having Seperation of Concerns. What is it? Why is it important? Let’s get started.

You will learn

  • What is Separation Of Concerns?
  • What are common examples of implementing Separation Of Concerns in software?

Software Design Principles

This is the second article in a series of articles on important Software Design Principles:

What Is Separation Of Concerns?

Separation Of Concerns is an important design and architectural principle.

Every element of a software application - a component, a layer,a package,a class or a method should have one concern and implement it well.

All methods with similar concerns will grouped into a class.

All classes with similar concerns will be grouped into packages.

So on and so forth.

Separation Of Concerns In Action

Layered Architecture

Organizing an application into separate layers is one way of separating out concerns.

For example, the following is the typical architecture of a web application:

image info

Here are some of the important responsibilities of each of these layers

  • The Web layer only bothers about how to present data to its users
  • The Business layer focuses on implementing the core application logic, correctly and efficiently
  • The Data layer takes responsibility of talking to the data store.

You can see that each layer has a concern and implements it well.

Organizing Microservices

Another good example of Separation Of Concerns is how you split your microservices. Have a look at the diagram below:

image info

All the microservices shown are part of a movie application. But each one of them has its own independent concern.

Identifying Common Components

Seperation of concerns is also an important factor in building common application and infrastructure components.

Since a large part of the functionality of microservices is common to all of them, it makes sense to extract out the common components. Here is an example:

image info

All microservices need features such as security and logging. By identifying common components in your service such as Security and Logging, and providing well defined interfaces with each microservice, the implementation of the microservices gets simpler.

The same is the case with common infrastructure components. Any microservice can interact with them and use their functionality.

A few examples of Seperation of Concern in infrastructure components

  • Naming Server - Microservice3 can locate the identity of Microservice2.
  • API Gateway - Centralized access to all microservices. You can implement cross cutting microservice concerns here.
  • Distributed Tracing and Centralized Logging - You can trace microservices and find out what’s happending behind the scenes.

Do check out our video on this:

image info


In this article, we looked at separation of concerns, and several examples of it in action - such as in a layered architecture, in the way microservices are split and organized, and in the way common components and infrastructure are identified and extracted out in a microservices architecture.

10 Step Reference Courses

Image Image Image Image Image

in28Minutes is creating amazing solutions for you to learn full stack and the cloud - Docker, Kubernetes, AWS, React, Angular etc. Click here for the complete catalogue of 30 Courses.

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.

Spring and Spring Boot Video Tutorials for Beginners

At in28Minutes, we are creating a number of tutorials with videos, articles & courses on Spring Boot for Beginners and Experienced Developers. Here's a list of video tutorials and courses for you

Object Oriented Software Design - Solid Principles - with examples

Software design is typically complex. Object oriented design takes it to the next level. There are a number of design patterns and other stuff to be aware of. Can we make things simple? What are the goals to aim for when you are doing object oriented design? SOLID Principles is a great starting point for Object Oriented Design.

Software Design - Open Closed Principle - with examples

Open Closed Principle is one of the SOLID Principles. You want your code to be easily extended. How do you achieve it with minimum fuss? Let's get started.

Software Design - What is Dependency Inversion Principle?

Dependency Inversion Principle is one of the important SOLID Principles. Dependency Inversion Principle is implemented by one of the most popular Java frameworks - Spring. What is it all about? How does it help you design good applications?

Introduction to Four Principles Of Simple Design

With agile and extreme programming, the focus is on keeping your design simple. How do you keep your design simple? How do you decide whether your code is good enough?

Software Design - Single Responsibility Principle - with examples

For me, Single Responsibility Principle is the most important design principle. What is Single Responsibility Principle? How do you use it? How does it help with making your software better? Let's get started.

REST API Best Practices - With Design Examples from Java and Spring Web Services

Designing Great REST API is important to have great microservices. How do you design your REST API? What are the best practices?

Designing REST API - What is Code First Approach?

Designing Great REST API is important to have great microservices. Code First approach focuses on generating the contract from code. Is it the best possible approach?

Designing REST API - What is Contract First?

Designing Great REST API is important to have great microservices. Contract First approach helps you in designing a great contract before implementing it. However, it does not come easy!