Skip to main content

Decompose Monolithic Application To Microservices

How To Decompose Application into Microservices.

After reading the previous two posts you all must be excited to implement microservice architecture to your application and that's good you should be ready to implement something new that might boost the application performance,  maintenance, scalability and will make your application future proof. But have you ever thought how will you be breaking your application into micro application i.e microservices. Think about it for some minute exercise your brain for some time before reading the below tutorial.

Now i am sure that you all might  have come through excellent ideas for breaking up your application in microservices. Please feel free to mention your valuable ideas in comment so that other or even me can be benefited by your ideas.

Now before breaking your application into micro-services you should consider following points.

Points to be considered before creating microservices.

  • Your each services should be easily testable.
  • Your application should be Cohesive.
  • Your application should be easily maintained by the help of small team(6-8 members).
  • Each micro-services should be loosely coupled.
  • Each team who are developing microservices should be self capable for end to end process from development to deployment.

Patterns to decompose your monolithic application into microservices

  • Decompose on basis of business capability.
  • Decompose on basis of subdomain.

Decomposition on basis of business

Whenever we develop microservices architecture we focus that our application is loosely coupled and support continuous delivery and development. Whenever changes come to our application it should impact only one service no multiple services as when the we have to deal with multiple services changes in order to comply with single change then we have to interact and depend on multiple team which will slow the process of development and cost productivity.

So when decomposing the application into microservices we can considers business capabilities. Business capability is something that business does to generate its value. We will take and example of school management system. 
In School management system from where the scholl generates it value.
  • Admission
  • Students
  • Stationery 
Then we can decompose our application on igh label into 3 services on which will deal with admission of the student, Students management, and Stationery.

Main problem with this structure is before decomposing one should have proper understating of business and its organisation for successful decomposition of the application.

Decomposition on basis of Subdomain

We can follow Domain-Driven Design(DDD) to apply this type of decomposition. In this Decomposition we have to define our domains in which our business will be working and also we have to identify the subdomain for each domain so that our each services will be small and easily manageable. We will take same example as we took above, of Student Management.
Here we can have domain as.
  • Admission
  • Students
  • Stationery
And further Admission can be decomposed into Accounts, Fees Management and etc
And Students can be decomposed into enrollment, Attendance and etc.
By this we will be having small modules or services which are easily manageable and maintainable. 


In this blog we learn about ways to decompose our monolithic application into small, maintainable, scalable services which are loosely coupled and help in continuous delivery and deployment. We covered about Decomposition on basis of business and Decomposition on basis of subdomain
Where in business decomposition we have to decompose our application by identifying  the business capability which generates revenue for the business and in Subdomain decomposition we learned the way do decompose the application in domain by domain driven design and further decomposing the into subdomains. 


Popular posts from this blog

Routing in Angular 7

What you will learn after reading this post.What is Routing in Angular 7.Basic routing of component in Angular 7.Active link in routing in Angular 7.Wild card routing in Angular 7.Child routing in Angular 7.1. What is Routing in Angular 7? Whenever in normal HTML web page we click on a link we are navigated to specific page given in that link. When we are navigated then entire view of the application is reloaded again which cost resources and this type of application is not single page application. 

Feature Modules in Angular 7

Feature Module Whenever we  create angular application we go on adding components to angular application. But as our application goes on increasing it become to much problematic to maintain such application. Every feature of our application is binded under single module which we call as app module. Which is root module of our Angular 7 application. While developing angular application without modularizing its features creates several problems  Application is not easily scalable.Application is tough to maintain.Application complexity makes it hard to understand. Solution Here feature modules comes for our rescue. Feature modules help angular applications to get modularised on basis of features present in our application. As our application grows we can divide our entire application in small feature using feature module. Feature modules helps in creating boundary that separates our specific functionality or say features. Feature modules communicates with other module or root module usin…

Monolithic Application Architecture

In regular web development process what do we do? We create one war file which contains all functionality, services, modules or all use cases related to our business. In this approach of development we do not focus to make our application modularise. We may be following modularization in our code but end product is not seperated. Every services, modules are bundled up in single war and this war is deployed on server so that our business will be available for outside world which can make a request to get the required resources. This native architecture of development is called Monolithic Architecture.

Creating Simple Hello World Application with SPRING BOOT

For creating a simple running web application with spring boot we do not have to do much. We just require to follow some simple steps and we are good to go. Unlike SpringMVC framework we do not. have to take care of all heck of configuration or XML file in one go we are all set with working mvc based web application.

Now we have to follow these steps.

Generate spring boot project from this url "" You can do the same using STS setting to.Importing the project in STS.

Lazy Loading of Feature Module in Angular 7

whenever angular application is loaded then its all modules are loaded eagerly i.e  entire application is loaded at client side on first request made to server. This cause over utilization of the resources and slows down the application at least at first time.

Just take example for E-commerce website which will have several module like order module, Feedback module, Cart Module, Product module and etc. But suppose your require to give feedback for some product you have bought and you visited to feedback page but now instead of loading just