Should I use Spring AOP?
java, spring, spring-mvc
Solution
I think I've actively used AOP in only a handful of projects over the years. In my work with Spring I use it rarely compared to most of the other Spring features. As such, I'm aware of it and what it can do, but I don't worry that I'm not ticking that particular box.
It's useful to understand what it is, and what it can do for you. However Spring is doing work for you already that leverages this, and you're likely to be using it already without knowing it! Being aware of AOP and how it works is the major issue here. As such, it sounds like you have this covered.
Problem
I am new to Spring and I want to clarify something about it. I developed an application for student management, for private institutes. It can record student details (address, phone number, enrolled courses, grade etc...), course details, payments from students, report generating module, details about lectures etc., However, I didn't use much of AOP to develop this app, except for rare cases like logging. But Spring AOP is a big part in Spring according to my knowledge. My question is, is AOP a big part of spring or am I missing the places where I should have used it (I am guessing I made newbie mistake of not using AOP much)? If so, can you clarify me where I should have used these concepts, so that I can learn from my mistake.