MICROSERVICES ARCHITECTURE
The fifth of our technology buzzwords is more IT-related. The microservices, also known as microservice architecture, is a method of developing software systems different than the traditional one and that has grown in popularity over the past years. It is an architectural style structuring an application as a suite of deployable services that implement some business capabilities.
There is not much out there about such architecture if just some observations and deductions from the common characteristics recognized. And just like there is no “official” definition, there is not one standard model represented in every system based on this architectural method. As we said, microservices can be decomposed into several component services, so that these services can be deployed, twisted, and redeployed independently. That way, the integrity of the application is not compromised by the changes. The microservice architecture is organized around business capabilities, and has cross-functional teams for its development, unlike the traditional “monolithic” development method. They design it in a way that it can cope with failure: as there are several services communicating together, one might go down; then, everything should be designed so that the neighboring services can keep on functioning. That adds substantial complexity to the microservice architecture, with regards to the monolithic one. Finally, the microservices don’t like old-fashion ways of centralized governance. Its developers aim at creating tools that can be used later by other people to solve similar problems: decentralized governance is preferred. Likewise, the data management is also decentralized: while monolithic systems use a single database across different applications, the microservices have a unique database managed by each service.
To sum up, the microservice architecture focuses more on products rather than projects, is organized around business capabilities, adjusts for service breakdown, and has a decentralized data management and governance. Such architecture enables the continuous delivery and deployment of complex and large applications and thus helps companies to evolve their technology stack. A warning, if we may give you one: many IT professionals advice not to start with microservices, but with a monolith. Keep it modular and then split it into microservices once the monolith architecture becomes problematic and you need to evolve.
No comments:
Post a Comment