This week's book giveaway is in the Servlets forum.
We're giving away four copies of Murach's Java Servlets and JSP and have Joel Murach on-line!
See this thread for details.
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes How the usage of an ORM impacts manageability and maintainability Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Murach's Java Servlets and JSP this week in the Servlets forum!
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "How the usage of an ORM impacts manageability and maintainability" Watch "How the usage of an ORM impacts manageability and maintainability" New topic
Author

How the usage of an ORM impacts manageability and maintainability

Joe O'Toole
Ranch Hand

Joined: Mar 02, 2009
Posts: 51
Hi

I have seen this question in a couple of different mock exams[SCEA] and each seem to give a different answer.

With the introduction of an ORM does this mean there is an extra component that needs to be managed and hence from the overall application/system perspective it has a negative impact on manageability?

Or - is it the case that using an ORM has a postive impact on manageability because it allows you to alter stored proc timeout values etc?

Also - is it accurate to say that the ORM has a positive impact on maintainability?

Thanks in advance

Joe
ntumba lobo
Ranch Hand

Joined: Oct 21, 2008
Posts: 180
Manageability has to do with how easy to monitor your running application and change its configuration. An ORM certainly provides features that can help improve it so yes it has got a positive impact especially for for the configuration side of thing.

Maintainability has to do with how easy to fix bugs in an application without impacting other functionalities. This has more to do with the design/architecture of your system. You can use all the bleeding edge frameworks you want in your system and still have a crappy maintainability. So the ORM in itself doesnt really have a significant impact on maintainability, be it positive or negative.
That's my view.


SCJP 5 , SCWCD 5, SCEA 5
 
It is sorta covered in the JavaRanch Style Guide.
 
subject: How the usage of an ORM impacts manageability and maintainability
 
Similar Threads
Question on Common system architectures
Definition Of Several Non-Functional Requirements
How heavy is reflection api
How various service-level requirements are related to each other?
conclusion in common architectures