Applying Cross-Cutting Concerns
As software projects evolve, they gain a certain structure, and if the team is disciplined, it will be somewhat consistent. When you get more team members, you might even document the structure. In addition to structure, you might also have ways of doing things and clear recipes of what needs to be done when creating different types of functionalities for the different parts of the stack. For global ownership, you might have these written down as well.
This is where cross-cutting concerns can come to the rescue. In this chapter, we will look at how to increase productivity for you as a developer by removing mundane tasks and improving consistency, and reducing risks. We will also look at how cross-cutting concerns can improve the maintainability of your software.
We will cover the following topics in this chapter:
- What are cross-cutting concerns?
- Leveraging the ASP.NET pipeline
- Authorization based on metadata or structure