No nonsense AOP

In his essay, Adrian Colyer elaborated on the idea of AOP in the simplest words. The concept of concept: implment makes everyone shine.

The concepts and requirements captured in the design are often the smallest unit of Change During the software evolution process. A ing between 1-1 to implementation can be easily added, deleted, and maintained. A 1-ing between 1-N and 1-N is much more difficult, because a concept changes, you have to update a lot of places-and you have to ensure that a change is not missed, and all the modifications must be strictly consistent.

When you start to consider AOP in this way, I hope you will see that AOP is more than just some of the attachments/Additives of existing software systems, it is an integral part of the software program design and implementation framework. This can also explain why AspectJ directly expands a programming language -- Java -- to integrate the concept of AOP. Remember, our goal is to achieve a relationship. As long as we have not achieved this balance, any more side will cause trouble, and AOP is to try to approach this balance as much as possible.

For the idea of AOP, refer to my idea of separation of responsibility to understand oo dp orm aop.