rojeckPrinciples of composition/aggregation reuse
The Composite/Aggregate Reuse Principle (CARP) is generally called the Composite Reuse Principle (CRP), which is defined as: try to use composite/aggregate instead of inheriting to achieve the purpose of reuse. The principle of composition/aggregation reuse is to use some existing objects in a new object to make it a part of the new object; the new object achieves the purpose of reusing existing functions by delegating to these objects held internally. Instead of getting existing functions th...
rojeck1. Salt
The application of Salting in HBase is to assign a random character to each rowkey prefix, so that the data is scattered in multiple different regions to achieve a balanced load. If the table region in HBase is distinguished according to the prefix of each letter, let's compare the changes before and after adding salt to the rowkey. First, we give a set of rowkeys before salt: rk001 rk002 rk003 According to the partition, the above rowkey is in the same region. Below we add salt to the above ...
rojeckSignificance of the Single Responsibility Principle
The single responsibility principle tells us: a class cannot do too many things. In a software system, the more responsibilities a class (a module, or a method) assumes, the lower the possibility of it being reused. A very typical example is the universal class. In fact, we can tell the truth: any conventional MVC project, in extreme cases, can use one class (or even one method) to complete all functions. But doing so will cause serious coupling and even affect the whole body. A class underta...
https://rss3.bio/0x8fC645e6a176F07395B8f44196d1443772FE9d57
rojeckPrinciples of composition/aggregation reuse
The Composite/Aggregate Reuse Principle (CARP) is generally called the Composite Reuse Principle (CRP), which is defined as: try to use composite/aggregate instead of inheriting to achieve the purpose of reuse. The principle of composition/aggregation reuse is to use some existing objects in a new object to make it a part of the new object; the new object achieves the purpose of reusing existing functions by delegating to these objects held internally. Instead of getting existing functions th...
rojeck1. Salt
The application of Salting in HBase is to assign a random character to each rowkey prefix, so that the data is scattered in multiple different regions to achieve a balanced load. If the table region in HBase is distinguished according to the prefix of each letter, let's compare the changes before and after adding salt to the rowkey. First, we give a set of rowkeys before salt: rk001 rk002 rk003 According to the partition, the above rowkey is in the same region. Below we add salt to the above ...
rojeckSignificance of the Single Responsibility Principle
The single responsibility principle tells us: a class cannot do too many things. In a software system, the more responsibilities a class (a module, or a method) assumes, the lower the possibility of it being reused. A very typical example is the universal class. In fact, we can tell the truth: any conventional MVC project, in extreme cases, can use one class (or even one method) to complete all functions. But doing so will cause serious coupling and even affect the whole body. A class underta...
https://rss3.bio/0x8fC645e6a176F07395B8f44196d1443772FE9d57
Subscribe to rojeck
Subscribe to rojeck
Share Dialog
Share Dialog
<100 subscribers
<100 subscribers
The Law of Demeter (LOD), sometimes called the Least Knowledge Principle (LKP), is defined as: a software entity should interact with other entities as little as possible. Each software unit has minimal knowledge of other units, and is limited to those software units that are closely related to the unit. The original intention of Dimit's Law is to reduce the coupling between classes. Since each class minimizes its dependence on other classes, it is easy to make the functional modules of the system function independent, and there is no (or very little) dependency relationship between each other. Dimit's Law does not want to establish a direct connection between classes. If there is a real need to establish a connection, I hope it can be conveyed through its friend class (intermediate class or jump class).
The Law of Demeter (LOD), sometimes called the Least Knowledge Principle (LKP), is defined as: a software entity should interact with other entities as little as possible. Each software unit has minimal knowledge of other units, and is limited to those software units that are closely related to the unit. The original intention of Dimit's Law is to reduce the coupling between classes. Since each class minimizes its dependence on other classes, it is easy to make the functional modules of the system function independent, and there is no (or very little) dependency relationship between each other. Dimit's Law does not want to establish a direct connection between classes. If there is a real need to establish a connection, I hope it can be conveyed through its friend class (intermediate class or jump class).
No activity yet