Summary
Cross-cutting concerns are an important part of a software application. In this chapter, you learned what cross-cutting concerns are and how to avoid scattering and tangling the solutions for cross-cutting concerns.
In this chapter, we learned how we can use DI, the decorator pattern, and AOP to implement cross-cutting concerns. This chapter provided some examples of common cross-cutting concerns, such as caching, configuration management, auditing, security, exception management, and logging. We also explored using a microservice chassis and/or the sidecar pattern when implementing cross-cutting concerns for microservices.
In the next chapter, we will take a look at the performance considerations that software architects make. We ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access