Fundamental traits of Micro Services

Micro Services work best when deployed in groups. Their numbers make them a complete system and today we will touch upon the underlying fundamental traits that make it possible for them to work the way they do. Single Purpose

A Micro Service should have only one single purpose. This means that it should not only do one single job but that it should have just that one single reason to be changed, stopped or paused as well.

This can sometimes become complicated for enterprises to follow since a single purpose can perhaps have sub-parts to it. In such a case do you create many micro services to handle each sub part or does one service handle the whole set?

To figure this out the other traits of Micro Services should also be looked into.


Micro Services do not share anything with any other services. The function and data of each one is its own. If one service needs something from another one it has to go through established communication protocols so as to not disturb the microcosm of the other.

Private Data

Each Micro Service manages its own data center and storage format. The reason for this is so that the data is not changed in any form due to being used by another service.

A Micro Service has established APIs and communication protocols for other services to ask for access to its data.

Private Deployment

Every Micro Service has its own deployment process, which means that there is no deployment library from which various micro services are deployed.

The reason behind this is that if there is a library or services then for each time an application runs a process a whole set of services will need to be deployed instead of just one service. This increases run time and reduces decoupling.

Just like with the data, if an application wants to deploy a Micro Service it needs to do so by using established APIs and communication protocols.

Since Micro Services tend to work in groups more often than not it is best practice to establish a system where each one gives regular status updates since keeping track of an entire architecture of Micro Services would become increasingly tough if they didn’t.

To stay updated with our series on Micro Services architecture follow us on twitter or subscribe to our blog.

Written By: Meghna Verma