• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • paul wheaton
  • Ron McLeod
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
Bartenders:

IBatis vs. JPA

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello. The company I recently joined has a very large Java "legacy" flagship web application that was first created about 8 years ago and has been added to piecemeal ever since. To put it mildly we are very much buried under a pile of technical debt. Recently we have had discussions about a new technology stack for when we redesign this app. For the persistence layer some of us were leaning toward JPA with Hibernate. Others wanted IBatis. With a redesign we would still be required to use some of the legacy db tables for some time to come. I have heard that IBatis might be better when using a legacy db structure and JPA being better when there is a new db design. Is there any truth to this? What would be better if we have a mix of legacy and new tables?

Thanks - Larry
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic