Links
- AspectJ in Action Read more about AspectJ in Action
- AspectJ in Action, 2nd edition Read more about what’s new in second edition
Twitter
- Loading tweets ...
- Follow @ramnivas on twitter.
Archives
- September 2009
- September 2006
- August 2006
- March 2006
- February 2006
- December 2005
- October 2005
- April 2005
- March 2005
- December 2004
- November 2004
AOP: Myths and realities
Posted on 2/14/2006 by Ramnivas
IBM developerWorks has published my AOP myths and realities article. In this article, I examine the following common myths around AOP and discuss their realities. Do you have or have you heard of other myths? Let me know. Perhaps I can address them in another article:
Update: There is a good discussion of this article at TheServerSide.com.
- AOP is good only for tracing and logging
- AOP doesn’t solve any new problems
- Well-designed interfaces obviate AOP
- Design patterns obviate AOP
- Dynamic proxies obviate AOP
- Application frameworks obviate AOP
- Annotations obviate AOP
- Aspects obscure program flow
- Debugging with aspects is hard
- Aspects can break as classes evolve
- Aspects can’t be unit tested
- AOP implementations don’t require a new language
- AOP is just too complex
- AOP promotes sloppy design
- AOP adoption is all or nothing
This entry was posted in Technology. Bookmark the permalink.
Comments are closed.