Micro-service architecture, a word that has grabbed everyone's attention and is gaining momentum everyday. So, what is micro-service, why does everyone want to shift to it and why do we need it? Let's understand the concept of micro-service architecture in detail.

The central idea behind micro-services is that some types of applications become easier to build and maintain when they are broken down into smaller, create able pieces which work together. Each component is continuously developed and separately maintained, and the application is then simply the sum of its constituent components. This is in contrast to a traditional, "monolithic" application which is developed all in one piece.

Monolithic Architecture

In a monolithic architecture, we will need just one code base. That code base will have all code related to all modules. For small projects monolithic architecture is preferred. The actual issue arises when the number of modules increases significantly.

Issues that could arise because of monolithic architecture are:

• It will be difficult to manage the code base
• Monolithic can also be difficult to scale when different modules have conflicting resource requirements
• Monolithic applications has a barrier to adopt new"
"