Chapter 17. Taking the next step
This chapter covers
- Approaching AOP adoption
- Applying AOP in various development phases
As we come to the end of this book, let’s consider some issues and practical solutions that will help your organization embrace AOP. In the last few years, having gone through its hype cycle, most developers and managers understand AOP’s value proposition. This is especially true for organizations that have embraced lightweight technologies such as Spring. Others still need convincing, especially when applying AOP that involves byte-code weaving. The industry could also use more guidance toward using an aspect-oriented approach in analyzing new problems and designing solutions.
In this chapter, we’ll address the adoption issue head on. I’ll make a few specific recommendations to help you be successful with AOP while managing risks with it. I’ll also discuss analysis and design based on AOP concepts.
Successfully adopting any technology requires that you take a pay-as-you-go approach. Such a path avoids undue risk, requires minimum upfront cost, and provides benefits at each stage. Let’s discuss a typical adoption path applied to enterprise application development. This path typically starts with Spring AOP.