Hi experts,
I recently read the blog-post “ABAP OO Design applied to ABAP RESTful Programming model (RAP) - Unmanaged scenario” from @AlwinPut and I wonder if similar OO design concepts can be applied to the managed scenario.
A real world application can easily grow up introducing several features that extend the BO behavior.
In this case the local class implementing the behavior handler becomes huge quickly, therefore it would be hardly maintainable.
It would be great to apply SRP and SoC principles developing each feature in a separate class; each determination, validation or action logic would be developed in its own class, while the behavior handler local class would act as a façade.
Adopting this approach even a complex app would be developed leveraging on simple short classes that would be easier to maintain (even by different developers within a team).
Do you have any suggestions to easily setup this architecture (handling the derived data types in a smart way too)?
Do you notice any drawback to point out related to this approach?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.