Downloaded 12 times
Uploaded byConcordia University
MSR2016 - An Empirical Study on the Practice of Maintaining Object-Relational Mapping Code in Java Systems
This document summarizes the findings of a study on maintaining object-relational mapping (ORM) code in Java systems. The study found that: 1) Most ORM code changes related to ORM queries and database mapping, while ORM performance configurations were rarely tuned. 2) There is limited tooling support for ORM code despite its popularity among Java developers. 3) ORM-related code changes were more scattered across files compared to non-ORM changes, possibly due to ORM's inability to completely abstract database accesses.
More Related Content
![Testclass [Autosaved]](https://cdn.slidesharecdn.com/ss_thumbnails/739334ac-668d-440e-ba47-823f8afaad75-160124183823-thumbnail.jpg?width=640&height=640&fit=bounds)
Similar to MSR2016 - An Empirical Study on the Practice of Maintaining Object-Relational Mapping Code in Java Systems
MSR2016 - An Empirical Study on the Practice of Maintaining Object-Relational Mapping Code in Java Systems
- 1. An Empirical Studyon the Practice of Maintaining Object-Relational Mapping Code in Java Systems 1 Mohamed Nasser, Parminder Flora Tse-Hsun(Peter) Chen Ahmed E. HassanWeiyi Shang Jinqiu Yang Michael W. Godfrey
- 2. Databases are essentialin modern large-scale software systems 2 Database
- 3. 3 Object-Relational Mapping (ORM) eliminatesthe gap between objects and SQL Database • Less boilerplate code • Object-DB translations are done automatically Java Classes Benefits over raw SQLs ORM Much less code and shorter development time
- 4. ORM provides anotherlayer of abstraction 4 ORM Database mapping code @Table(name = “user”) Performance configuration query.cache() ORM query code User u = q.getSingleResult();
- 5. 5 ORM is nota silver bullet Using ORM comes with some hidden costs… We have been working on helping developers improve ORM code for the past few years
- 6. Developers are oftennot aware of database access Wow! I don’t need to worry about DB code! ORM code with performance anti-patterns 6 Bad system performance The performance impact can be SIGNIFICANT (ICSE 2014)!
- 7. ORM is hardto configure 7 Hundreds of ORM performance-related configuration Un-optimal ORM configuration is common and causes significantly performance problem (TSE 2016)! Bad system Performance if configured incorrectly
- 8. Studying maintenance activitiesof Java ORM code 8 Expect: ORM-related changes are localized Expect: Frequently tuning configurations Expect: Tooling support due to ORM popularity
- 9. Studied Java systems Largeopen-source e-commence system Enterprise system 9 Portal Content management system
- 10. Studying maintenance activitiesof Java ORM code 10 Expect: ORM-related changes are localized Expect: Frequently tuning configurations Expect: Tooling support due to ORM popularity
- 11. Lack of bugdetection tool support for Java ORM 11 Coverity PMD Google error-prone Facebook InferFindBugs More than 67% of Java developers use ORM, but there is limited tooling support (ICSE SEIP 2016)
- 12. Studying maintenance activitiesof Java ORM code 12 Expect: ORM-related changes are localized Expect: Frequently tuning configurations Expect: Tooling support due to ORM popularity No! There is limited tooling support
- 13. Studying maintenance activitiesof Java ORM code 13 Expect: ORM-related changes are localized Expect: Frequently tuning configurations Expect: Tooling support due to ORM popularity No! There is limited tooling support
- 14. ORM configurations arerarely tuned 14 Most ORM code changes are related to ORM queries (35%) and ORM database mapping code (55%) ORM performance configurations are rarely tuned (less than 10%)
- 15. Studying maintenance activitiesof Java ORM code 15 Expect: ORM-related changes are localized Expect: Frequently tuning configurations Expect: Tooling support due to ORM popularity No! There is limited tooling support No! ORM configurations are rarely tuned
- 16. Studying maintenance activitiesof Java ORM code 16 Expect: ORM-related changes are localized Expect: Frequently tuning configurations Expect: Tooling support due to ORM popularity No! There is limited tooling support No! ORM configurations are rarely tuned
- 17. ORM code changesare more scattered 17 0 2 4 6 8 10 12 14 ORM non-ORM Medianmodifiedfilesinacommit Such high change scatteredness may be caused by ORM’s inability to completely abstract DB accesses
- 18. Studying maintenance activitiesof Java ORM code 18 Expect: ORM-related changes are localized Expect: Frequently tuning configurations Expect: Tooling support due to ORM popularity No! There is limited tooling support No! ORM configurations are rarely tuned No! ORM code changes are more scattered
- 19.
- 20.
- 21.
- 22.
- 23.
- 24.
- 25.
- 26.
- 27. 27 Tse-Hsun (Peter) Chentsehsun@cs.queensu.ca