This is a bit long Paper, presents Adaptive Object-model (AOM), which can be thought of it as more flexible than conventional object-oriented design (OOD). Good examples are given and style is explained in details along with advantages and disadvantages.Very interesting concept for OO developers as i am one of them…
In AOM system, classes and their attributes and methods are represented as metadata and this model will be stored in database and system interprets and translates these models. So changing the application or class does not require changing the actual code but just the metadata. Changes to metadata are immediately interpreted and reflected in the running application and doesn’t need to deploy the code changes or make the system offline to release the new version. I think this is a very nice feature compared to conventional OOD systems.
I think this architectural style works great for system which needs flexibility and runtime configuration. I never work on this type model but definitely like to keep it in mind for future, but it was very cool to see the system be automatically changed in production whenever there was a change in the metadata.
It was mentioned in the paper that these type of projects are hard to understand and maintain not completely sure why can’t they be easily understood. Prof. Johnson may reveal the background in the evening class.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment