Cross-cutting Concern

before we jump into understanding what are cross-cutting concerns, we’ll have to understand what a concern is. A concern is a part of a system divided on the basis of functionality. It can be as general as the details of the database interaction or as specific as performing a primitive calculation. Usually, code can be separated into logical sections, each addressing separate concerns.

Concerns can be categorized into two types, core-concerns, and cross-cutting concerns. In short cross-cutting concerns are shared across multiple application modules. They represent functionalities for secondary requirements. for example logging, security, and data transfer are concerns that are needed in almost every module of an application, hence also called system-wide concerns.

bonus:

Core concerns represents single and specific functionality for primary requirements. e.g. business logic.