Microservice Architecture - Motive Shift to Target
The article by Martin Fowler and James Lewis, which describes the merits of Microservice Architecture, says:
Enterprise application - an application built as a whole. ANY change in the system leads to a reassembly and deployment of a new version of the server part of the application.
It is clear the desire of the authors to be advocates of the “Microservice Architecture”, but the use of such definitions as ANYONE, ALWAYS, NEVER speaks about too emotional attitude to the subject. There is an attempt to captivate the reader with emotions, turn off his brain. When authors use such exaggerations, the devil must be hiding somewhere. So where is he, horny?
')
In my opinion, an application in which any change leads to a reassembly is a bad application. Very bad. In a good application FAR, not every change leads to a reassembly. I know a lot of applications (and I constantly do these), in which the emergence of new functionality does not lead to reassembly of the application. To do this, the application must be able to interpret metadata (for example, settings), exchange standardized messages and perform useful work. A computer is an interpretation device, a good application must be done in the same paradigm.
There are prerequisites for creating metadata-based applications. Each area of ​​activity has a limited range of routine operations, data entry forms and display. For data entry and display, the UI can be quite formally described and interpreted by the application. Not only information entry forms, but also menus, questionnaires, filters, reports, etc. can be described and interpreted. This does not mean that Microservice Architecture is not
need This means that applications should be built using a variety of approaches, avoid cultivating a monoculture, do not shoot the gun on sparrows, i.e. turn on the brain and not build bad applications based on the Microservice Architecture. We must try to avoid shifting the motive to the target, so that the Microservice Architecture is for applications, and not for the application for Microservice Architecture.
It is clear that fashion destroys the head, propagandists influence the subconscious, create pseudo-concepts. But as the song says:
You write to your notebook
On every page.
No need to lose your head
Do not rush.
No need to lose your head
what if it comes in handy.
Enterprise application - an application built as a whole. ANY change in the system leads to a reassembly and deployment of a new version of the server part of the application.
It is clear the desire of the authors to be advocates of the “Microservice Architecture”, but the use of such definitions as ANYONE, ALWAYS, NEVER speaks about too emotional attitude to the subject. There is an attempt to captivate the reader with emotions, turn off his brain. When authors use such exaggerations, the devil must be hiding somewhere. So where is he, horny?
')
In my opinion, an application in which any change leads to a reassembly is a bad application. Very bad. In a good application FAR, not every change leads to a reassembly. I know a lot of applications (and I constantly do these), in which the emergence of new functionality does not lead to reassembly of the application. To do this, the application must be able to interpret metadata (for example, settings), exchange standardized messages and perform useful work. A computer is an interpretation device, a good application must be done in the same paradigm.
There are prerequisites for creating metadata-based applications. Each area of ​​activity has a limited range of routine operations, data entry forms and display. For data entry and display, the UI can be quite formally described and interpreted by the application. Not only information entry forms, but also menus, questionnaires, filters, reports, etc. can be described and interpreted. This does not mean that Microservice Architecture is not
need This means that applications should be built using a variety of approaches, avoid cultivating a monoculture, do not shoot the gun on sparrows, i.e. turn on the brain and not build bad applications based on the Microservice Architecture. We must try to avoid shifting the motive to the target, so that the Microservice Architecture is for applications, and not for the application for Microservice Architecture.
It is clear that fashion destroys the head, propagandists influence the subconscious, create pseudo-concepts. But as the song says:
You write to your notebook
On every page.
No need to lose your head
Do not rush.
No need to lose your head
what if it comes in handy.
Source: https://habr.com/ru/post/337526/
All Articles