Software Design - Separation Of Concerns - with examples


Image


Software architects and programmers love having Separation 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?

Free Courses - Learn in 10 Steps

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

Separation 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 Separation 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 happening behind the scenes.

Do check out our video on this:

image info

Summary

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.

Best Selling Udemy Courses

Image
Image Image Image Image Image Image Image Image Image

Join 450,000 Learners and 30+ Amazing Courses

350,000 Learners are learning everyday with our Best Selling Courses : Spring Boot Microservices, Spring, Spring Boot, Web Services, Hibernate, Full Stack React, Full Stack Angular, Python, Spring Interview Guide, Java Interview, Java Functional Programming, AWS, Docker, Kubernetes, PCF, AWS Fargate and Azure


Do not know where to start your learning journey? Check out our amazing learning paths:
Learning Path 01 - Spring and Spring Boot Web Applications and API Developer,
Learning Path 02 - Full Stack Developer with Spring Boot, React & Angular,
Learning Path 03 - Cloud Microservices Developer with Docker and Kubernetes,
Learning Path 04 - Learn Cloud with Spring Boot, AWS, Azure and PCF and
Learning Path 05 - Learn AWS with Microservices, Docker and Kubernetes


Subscribe

FREE COURSES



Related Posts

Writing Integration Tests for Rest Services with Spring Boot

Setting up a basic REST Service with Spring Boot is a cake walk. We will go one step further and add great integration tests!

Integrating Spring Boot and Spring JDBC with H2 and Starter JDBC

Learn using Spring Boot Starter JDBC to connect Spring Boot to H2 (in memory database) using Spring JDBC. You will create a simple project with Spring Boot. You will add code to the project to connect to a database using Spring JDBC. You will learn to implement the basic CRUD methods.

JUnit Tutorial for Beginners in 5 Steps

JUnit Tutorial for Beginners in 5 Steps. Setting up a basic JUnit example and understanding the basics of junit.

JPA and Hibernate Tutorial For Beginners - 10 Steps with Spring Boot and H2

JPA and Hibernate in 10 Steps with H2 - Setting up a basic project example with Spring Boot and in memory database H2. Its a cake walk.

Spring Boot Tutorial For Beginners in 10 Steps

Introduction to Spring Boot in 10 Steps. Learn the basics of Spring Boot setting up a basic project example with Spring Boot.

Spring Framework Tutorial for Beginners - Your First 10 Steps

Learn the basics of Spring Framework setting up a very simple example.

JPA and Hibernate Tutorial using Spring Boot Data JPA

Complete journey starting from JDBC to JPA to Spring Data JPA using an example with Spring Boot Data JPA starter project. We use Hibernate as the JPA Implementation.

Creating a Web Application with Spring Boot with JSP

Setting up a basic web application with Spring Boot is a cake walk. We will create a simple web application using Spring Initializr and add JSP features to it.

What is Spring Boot Auto Configuration?

Auto Configuration is the most important feature in Spring Boot. In this tutorial, we will learn important concepts about Auto Configuration with a couple of examples.

Unit Testing Rest Services with Spring Boot and JUnit

Setting up a Basic REST Service with Spring Boot is a cake walk. We will go one step further and add great unit tests to our RESTful Service.


Search