I can’t tell if it’s really less spoken for, I don’t know specific research on this. However, AOP has not disappeared and if we talk enough yes, just see the amount of questions just in the tag aop in Soen, searching for aop also at Soen.
If your biggest interest is in Spring projects, you can start by here
In Spring as a whole AOP is widely used. When you use Spring MVC, Data, Social, Transaction Management, etc. every part of it is using AOP somehow, even if you don’t realize it so clearly. For example, only by changing in a class of which the object(s) (s) is managed by the Spring context of @Component
for @Service
(and vice versa) will have differences
In Java EE AOP is also quite present, for example note the interceptors
, this just speaking of the use in java technologies, here you may see a new support list on some platforms, whether native or not.
How much is worth studying, depends, AOP is a paradigm that coexists with others, you may one day need, may not, so can not talk whether it still compensates or not, depends on context.
In many cases quite useful; in others, quite obscure. Just use Spring projects and you’ll find yourself thinking where is this log, for it is largely done logging using aspects, which can make it difficult to follow execution flows in certain cases.
Today too little is said about the wheel, but this does not mean that the technology is irrelevant. Right here in SOPT, the tag [tag:orientation-to-objects] is one of those that appear on the front page, due to the relative amount of questions on the subject.
– Luiz Vieira
Really, it is something to be considered, but for me it seems concrete that studying this paradigm will be useful for at least two aspects: (1) will allow you to work well with the vast majority of modern languages and more easily with the others and (2) will facilitate that you learn the other so many existing paradigms, among them the SOA (Service Oriented Architecture) and the AOA (Agent Oriented Architecture).
– Luiz Vieira