Shulou(Shulou.com)06/03 Report--

This article mainly explains "what is a single architecture". The content of the explanation is simple and clear, and it is easy to learn and understand. Please follow the editor's train of thought to study and learn "what is a single architecture".

Modular software development

Modular programming is a scheme put forward from the late 1960s to the 1970s. It is a well-defined evolution from classes to more coarse-grained units of code. Programming languages use different levels of clarity to achieve modularity.

For example, JAVA has a default level of visibility at the class level and a public level, which means that the class is visible only within the package (module) to which it belongs, while the public level means that the class is visible both inside and outside the package (module).

Component-based software development

Components are another modular style. As I mentioned in my previous article, components are modules divided by domain concepts. Ideally, they are separate "applications" that can make up applications. The old examples are pipes and filter architectures that are widely used in Unix systems. For example, we can use the command ps-ef | grep php. Another example is that Netflix uses micro-services as a component of the application.

The organizational style of code, like modular software development, has existed since the late 1960s.

Modern monomer

Now, the monolithic architecture style simply means that all application code is deployed and run in a single process with a single node. We think it will use modules and components, although this is often not the case.

Here are two keywords "deployment" and "node" to be well understood. The first word "deployment" refers to the way the runtime code is organized, regardless of whether the code is physically stored in one or more code bases. The second word "node" means that even if we deploy the application to multiple servers in the case of scale-out, it is still a single unit.

On a single-node server, all modules of a single unit are concentrated in the same memory image and run as a single process on a single node. Communication between modules is carried out on the same stack and within the heap through standard process calls. A single memory image makes the application monolithic. If the module runs in a different process, the communication becomes IPC (interprocess call). As modules enter different process boundaries, you will face the challenge of distributed computing. This enters the category of micro-services. Thanks to dban for your feedback.

Despite its notoriety, this style can still work well in large applications. It's just that it's not good enough under the following conditions:

Different domain components need to be independently scalable

Different components require different programming languages to write

Independently deployable, because our release frequency is faster than the continuous delivery pipeline of a code base, the deployment of our own release becomes slow due to the need to wait for other release deployments, or the deployment queue grows too fast to respond in time.

At this point, we need to split the monomer into different applications in a service-oriented architecture style (described in more detail in the next article).

Anti-pattern: big mud ball / spaghetti structure

The "big mud ball", also known as the spaghetti structure, is an anti-pattern of this style. In this anti-pattern, the packet structure and relationship are very vague, structured cohesion and encapsulation are completely or rarely, dependencies are irregular, and subsystems are difficult to distinguish, and it is also difficult to modify and reconstruct. The system is obscure, sticky, fragile and rigid: it's a big mud ball!

Thank you for your reading, the above is the content of "what is a single architecture", after the study of this article, I believe you have a deeper understanding of what is a single architecture, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.