It reads like the chicken and egg story only in the case of Micro Services and Micro Segmentation it is very easy to think that they come as a package deal and thus confuse the two.
As we have often discussed on the Captain Dash blog, Micro Services refer to a set of services or mini applications making up the application architecture of an organization.
An organization can either break apart an existing Monolithic application to create Micro Services or it can create its architecture as a combination of several Micro Services from scratch.
Micro Segmentation on the other hand deals with breaking up of a network itself. This could be done for several reasons, foremost of which is security.
The point to note though is that when a team uses the Micro Services approach to their architecture a natural bifurcation of the network occurs thus leading to Micro Segmentation. This is also the reason why there can be confusion between the two.
Another significant use for Micro Segmentation is that aside from taking the pressure off of one large network is that it isolates disruption when services need to be changed or upgraded. In case of a single large network one change can have domino effect on the whole network.
Micro Services and Micro Segmentation
In brief these are both methods of segmenting a Monolithic architecture in different domains and turning them into smaller, more scalable and secure components.
Just because a team uses one approach it doesn’t automatically mean that the other follows. Though it is best practice to employ both for optimization.
While one cannot say which one comes first, as a general rule it has been observed that if a team uses Micro Services then Micro Segmentation is quick to follow. On the other hand the employment of Micro Segmentation does not necessarily result in the use of Micro Services by a team.
If your organization has made the switch to Micro Services or to Micro Segmentation we would love to hear which came first for you.
Written By: Meghna Verma