Example: Cross Cutting Concerns of an Application
Example: Cross Cutting Concerns of an Application
Join the DZone community and get the full member experience.
Join For FreeDiscover how you can get APIs and microservices to work at true enterprise scale.
Eight Core Concerns
- Database Access
- Data Entities
- Worker
- Result Processing
- Process Flow Manager
- Email/Notification
- Error Handling
- Logging
Of these eight, five were actually cross cutting concerns.
5 Cross Cutting Concerns
- Database Access
- Data Entities
- Email/Notification
- Error Handling
- Logging
These five cross cutting concerns were determined after I created an aspect oriented model to help identity the system components that could be factored out into separate components. These separated components would then be included in the system so that they could be used by various other components. These five components allow all of the other components to access the database, store data, send notifications, handle errors, and log all system events. Thus, these components are used to share unique aspects to the system via their implementation.
The use of Aspect Oriented Architecture greatly helped me define what components I needed to create and what each of those components could do. It also showed how all of the other aspects depended on each other so that each component did not have to re-implement code that was already created in the existing system.
APIs and microservices are maturing, quickly. Learn what it takes to manage modern APIs and microservices at enterprise scale.
Like This Article? Read More From DZone
Published at DZone with permission of Todd Merritt , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}