The Return of Aspect Oriented Programming

nmehner

My problem with AOP has always been that it makes the simple case trivial and the hard case much harder. Looking at transactions: The 99% solution is trivial: Every service call is a transaction. AOP can save me a few lines for every method and things look much cleaner. But then comes the huge excel upload that is performance critical. Batch more service calls to fetch additional information in the background, commit every so-and-so records in a loop depending on the data size, do a custom roll-back if things fail. And suddenly this whole separation of concerns breaks down and creates a huge mess. The simple case saves a few minutes, the complicated case causes weeks of depression. Not a good tradeoff from my experience. An LLM adding to the confusion by only sometimes getting things right and explaining that the separate documents are always valid, except when they are not, well, sounds like a fun experience.