What is a micro service?
Small, individually, independently deployable application components that are self-contained and exposed through lightweight http based APIs. Here the independence of the of those components is really important because it has lot of ramifications in terms of how manage large-scale deployments of this architecture. Some people may say micros services are contrary to service oriented architecture. Actually, that's not true, Micro services are extension or evolution of service oriented architecture. The same principles still hold true but then it fixes lots of problems that were there in the service oriented architecture like large ESBs (Enterprise service bus), unwieldy configurations and scalability issues. It breaks that down into small reusable components that now you can scale individually or you can manage individually, so it gives lot more flexibility.
Why IT industry has moving towards Micro Services?
Well, obviously Agile and Scrum are big factor in this because here the organizations wants to deliver things quicker., DevOps is the other key word you know key to this. In micro service architecture world we have lots and lots of deployments. So we need a good CI/CD pipeline and ways to deploy these services as opposed to the old traditional way of doing things. A person, I mean a developer who is responsible for that particular service end to end all the way to production. So it's changing and flipping how organizations hand things off to productions because the same person is responsible for it from the start all the way to be running in production.
Some comparisons between Micro services vs. SOA.
Micro service architecture trying to achieve many of the same things (enable the creation of business functions as isolated components) but at a very different scale. SOA evolved to become focused on the enterprise scale (though some would say that wasn't the original intent). Micro services are primarily at the application scale.
Both the components describe the actual implementation of a business function, They differ primarily in granularity, but also arguably in maintainability, agility etc.
Micro services is primarily an application architecture concept. some of the ideas might be applicable at an enterprise level, but that rather depends on the size and shape of your enterprise.
SOA is an enterprise level architectural concept for enabling more effective direct integration between applications. you can certainly bring micro services techniques into that space to help build some of the componentry in new ways, but beware when the scopes overlap as some of the core principles are opposing.
Small, individually, independently deployable application components that are self-contained and exposed through lightweight http based APIs. Here the independence of the of those components is really important because it has lot of ramifications in terms of how manage large-scale deployments of this architecture. Some people may say micros services are contrary to service oriented architecture. Actually, that's not true, Micro services are extension or evolution of service oriented architecture. The same principles still hold true but then it fixes lots of problems that were there in the service oriented architecture like large ESBs (Enterprise service bus), unwieldy configurations and scalability issues. It breaks that down into small reusable components that now you can scale individually or you can manage individually, so it gives lot more flexibility.
Why IT industry has moving towards Micro Services?
Well, obviously Agile and Scrum are big factor in this because here the organizations wants to deliver things quicker., DevOps is the other key word you know key to this. In micro service architecture world we have lots and lots of deployments. So we need a good CI/CD pipeline and ways to deploy these services as opposed to the old traditional way of doing things. A person, I mean a developer who is responsible for that particular service end to end all the way to production. So it's changing and flipping how organizations hand things off to productions because the same person is responsible for it from the start all the way to be running in production.
Some comparisons between Micro services vs. SOA.
Micro service architecture trying to achieve many of the same things (enable the creation of business functions as isolated components) but at a very different scale. SOA evolved to become focused on the enterprise scale (though some would say that wasn't the original intent). Micro services are primarily at the application scale.
Both the components describe the actual implementation of a business function, They differ primarily in granularity, but also arguably in maintainability, agility etc.
Micro services is primarily an application architecture concept. some of the ideas might be applicable at an enterprise level, but that rather depends on the size and shape of your enterprise.
SOA is an enterprise level architectural concept for enabling more effective direct integration between applications. you can certainly bring micro services techniques into that space to help build some of the componentry in new ways, but beware when the scopes overlap as some of the core principles are opposing.
Comments
Post a Comment