Microservices Architectures - Non Functional Requirements - Reusability

In this article, we explore the important non functional requirement called Reusability.

What you will learn

  • What Is Reusability?
  • Why is Reusability important?
  • How do you improve Reusability of your components?

Non Functional Requirements and Microservices

This is the part of a series of articles on Non Functional Requirements:

What Is Reusability?

Suppose you have worked on a project to create a microservice - Microservice A - and you are now working on a new project - Microservice B.

Question to ask is:

How much of the earlier implementation of Microservice A, how many modules and components (technical and infrastructure) can you reuse in the next microservice?

You would prefer your applications to be built with reusable components, because it avoids unnecessary duplication of code and effort.

Improving Reusability

The common approach to improving reusability involves one thing - “Build your system in a modular manner”.

Have a look at the following microservice architecture: image info

Instead of having a single monolith application, system is organized into modules. Over here, we have identified several common components, such as Security and Logging, which have logic that can be used across microservices.

Also visible are several common infrastructure components, such as NamingService, CentralizedLogging and APIGateway. These offer common services to several microservices.

Once you have such common modules organized, each microservice would only be responsible for its own business logic. That makes it very easy to augment the system by adding new microservices, because there is no need to replicate the common components logic any more. The new service also just needs to manage its own business logic. The functionality of the common component can be reused.

Reusability at Code Level

You would want to avoid duplication in your code. The best way to ensure good low level design (methods and classes) is to ensure you are following the 4 Principles of Simple Design.

  • You have great tests
  • Your code is readable
  • Your code has minimum duplication
  • Your application, components, packages, classes and methods are as small as they can be


In this short article, we talked about application reusability as a measure of how much functionality can be reused indifferent scenarios. Reusability can reduce duplication of code and effort. The most suitable way to improve the reusability of an application is to make its design modular.

Do check out our video on this:

image info

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

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.

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?