Microservice architecture is a variant of the (SOA) service-oriented architecture structural style is arranges an application as a collection of loosely-coupled services.
Big applications will be divided into minor independent service units in a microservices architecture.
Introduction:
A microservice is not a layered path within a monolithic application (for example, the web controller or the backend-for-frontend). It is a free-standing piece of business functionality with clear interfaces and may implement a layered architecture through its internal components.
Some rules are followed to keep in mind while developing a Microservice-oriented application.
- Coupling − All microservices should be loosely coupled with one another such that changes in one microserver will not affect the other microservers.
- Business Goal − Each service unit of the entire application should be micro and capable of delivering one specific goal.
- Independent − Each microservice is independently deployable.
Let take one example of an e-commerce website like Amazon or flip card. Each E-commerce portal has user management, order management, check-in, payment management, delivery management, etc. One successful order needs to pass through all of these modules. They communicate with other third-party vendor software for specific needs and with each other.
History:
As early as 2005, Peter Rodgers introduced the term “Micro-Web-Services.”
In 2007, Juval Löwy, in his writing and speaking, called for building systems in which every class was a service. Löwy realized this required using a technology that can support such granular use of services.
While conventional distributed systems of that era relied on proprietary communications protocols, microservices took advantage of open standards such as JSON, HTTP, REST, and XML.
Microservices specialize in an implementation approach for service-oriented architectures (SOA) used to build flexible, independently deployable software systems.
Benefits:
- Modularity:
Modularity makes the application easy to develop, test, and understand, becoming more resilient to architecture erosion. - Scalability:
Since microservices are implemented and deployed independently, they run within independent processes and can be monitored and scaled separately. - Distributed development:
Distributed development is parallelizing development by enabling small autonomous teams to independently deploy, develop, and scale their respective services. It allows the architecture of a particular service to appear through continuous refactoring. - Integration of heterogeneous and legacy systems:
Microservices is considered a viable means for modernizing existing monolithic software applications. There are experience reports of several companies that have successfully replaced their existing software with microservices are in the process of doing so.
Resourse:
https://en.wikipedia.org/wiki/Microservices
https://medium.com/microservicegeeks/an-introduction-to-microservices-a3a7e2297ee0
https://www.tutorialspoint.com/microservice_architecture/microservice_architecture_introduction.htm#:~:text=Microservice%20is%20a%20service%2Dbased%20application%20development%20methodology.&text=Microservice%20is%20the%20process%20of,serve%20only%20one%20business%20need
Disclaimer:
Wherever any material is quoted as sourced from the published text with publishing rights vested in an individual, it is stated that it is a pure quotation and has no intention to claim it as our own.
Image Source: www.freepik.com
