In this article, we explore the important non functional requirement called Modularity.
What you will learn
- What Is Modularity?
- Why is Modularity important?
- How can you build more Modular systems?
Free Courses - Learn in 10 Steps
- FREE 5 DAY CHALLENGE - Learn Spring and Spring Boot
- Learn Spring Boot in 10 Steps
- Learn Docker in 10 Steps
- Learn Kubernetes in 10 Steps
- Learn AWS in 10 Steps
Non Functional Requirements and Microservices
This is the part of a series of articles on Non Functional Requirements:
- 1 - Microservices Architectures - Non Functional Requirements
- 2 - Security
- 3 - Web Application Security And OWASP - Top Ten Security Flaws
- 4 - Maintainability
- 5 - Scalability
- 6 - Performance
- 7 - Reusability
- 8 - Reliability
- 9 - Modularity
- 10 - Availability
- 11 - Portability
What Is Modularity?
What you are looking at is an instance of a microservices architecture:
How would you build such a system?
A decade back, the entire functionality of what you see in the picture, would be provided by a single monolith application.
As we moved on from monolith to service-oriented to microservices architecture, we build more modular applications.
We focus on identifying multiple microservices, common components that have well defined interfaces, and common infrastructure components that are the building blocks of the application’s technical capabilities. This is what is called a modular architecture.
Modularity applies at multiple levels:
- How do you architect your applications?
- How do you design your components?
- How do you design your classes?
What is Separation of Concerns?
The cornerstone of modular architecture is separation of concerns.
This involves identifying a functionality that can be handled separately, and defining an application, a component, a package or a class to do it.
For example, the security component handles the low-level details of user authentication and authorization. These include the specifics of how user credentials are stored, how user’s access related information is stored, and the like.
Security component provides a well-defined, consistent interface. When a microservice needs to authenticate the user, it would send a request to the security component. The microservice will not need to worry about how the authentication is done.
While implementing modularity, you try and create components with separate responsibilities. This makes reusing the components and creating new microservices easy.
Building reusable components
Let’s look at an example.
Suppose Microservice1 wants to check of the user has provided the right credentials, and whether he has access to a particular resource. It clearly needs to make use of the Security component. If it finds the need to log a message, it makes use of the Logging component. If Microservice1 wants to find out where Microservice3 is deployed, it submits a query to the NamingServer infrastructure component. The component in turn, provides a response with the location.
There are essentially two kinds of components:
- Common Utility Components and Frameworks : There are very technical in nature, each of them being implemented as separate modules. In Java applications, these would be JARs. Microservice1 would call methods in the JARs and use their functionality.
- Infrastructure Common Components : These are independently deployable common applications - Naming Servers, API Gateways etc.
The term component is used to describe a part of the application, that is independently reusable.
Do check out our video on this:
In this article, we explored the meaning of the term modularity, when applied to application architecture. We saw that modern microservices implement something separation of concern, to achieve modularity. They do this by identifying and extracting out functionality into common components, both technical and infrastructure. These components have well defined interfaces, and makes the addition of new microservices to the application, relatively easy.