Aspect-oriented programming (AOP) addresses a common functionality, that spans across an application, but cannot be otherwise abstracted in a single module using traditional object-oriented techniques. This repeated functionality is often referred to as cross-cutting concerns. A common example is logging—normally, loggers are created within classes and then their methods are called inside the methods of the classes. This helps with the debugging and tracing of events in an application, but it is not really related to the actual functionality in any way.
AOP recommends that cross-cutting concerns are abstracted and encapsulated in their own modules. In the next few subsections, we will look into how AOP improves code and also makes cross-cutting concerns easily extendible.