Aspect-oriented programming (AOP) separates uniform cross-cutting concerns, such as logging, from business logic. A framework weaves that logic into selected methods at runtime or compile time. section 4.3.2 section 4.5.3
Logging an order service
A plain OrderService can keep saveOrder focused on business logic. A framework can weave a log call before the method runs, without adding that call to the service itself. section 4.3.2
class OrderService
{
// The framework magically injects or provides access to this
saveOrder(order) {
_logger.Log("Executing SaveOrder..."); // <-- "Woven" in
// Just pure business logic...
}
}See the woven version: the framework adds a log call before saveOrder’s business logic. section 4.3.2
AOP suits uniform behavior, but it is not a cure-all: woven logic may lack useful business context, and extensive weaving can add build size and runtime overhead. For simpler cases, injecting a shared service is another way to keep concerns separate. section 4.3.2 section 4.5.3

