• 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
  • Jeanne Boyarsky
  • Ron McLeod
  • Liutauras Vilda
  • Paul Clapham
Sheriffs:
  • paul wheaton
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Piet Souris
Bartenders:
  • Mike London

Persistence : Portability

 
Ranch Hand
Posts: 93
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
We generally say that such and such framework will allow us to have portability.
But how many times does it happen when we really change database? or for that matter our ORM/persistence provider.
In my company we use hibernate but still have iBatis for oracle stored procedures.
 
Ranch Hand
Posts: 121
IntelliJ IDE Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I've worked on a project where we used MySQL in the development environment and Oracle in production.
In another project, the client decided to change from MS-SQL to Oracle.
 
Bartender
Posts: 10336
Hibernate Eclipse IDE Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
We change databases all the time. We support a variety of database tyes and versions in production. We also swap to an HSQLDB instance in our unit test run that is created in a known state by our tests. Very useful.
 
author and cow tipper
Posts: 5006
1
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I often see databases change, but you are right, we quite often see the old database persistence mechanism sticking around. DAOs are supposed to make switching implementations easy, but few people actually want to do it.

I think your general tone is probably correct. We do alot to keep our applications and our persistence layer flexible and pluggable, but when so much is at risk, professionals are very hesitant to plug in anything new.

-Cameron McKenzie
 
Padmarag Lokhande
Ranch Hand
Posts: 93
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thank You all for the inputs.
 
author
Posts: 181
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Padmarag Lokhande:
We generally say that such and such framework will allow us to have portability.
But how many times does it happen when we really change database? or for that matter our ORM/persistence provider.
In my company we use hibernate but still have iBatis for oracle stored procedures.



So there is application portability and db portability. I think persistence frameworks are getting good at the application portability.

DB portability is usually harder. I would say though that if you can be like 80%-90% portable, then you are in good shape.

SQL frameworks actually become harder to port because SQL developers get good at writing database tuned SQL (Usually have some DBA do the tuning). A framework like iBatis which externalizes SQL can be good for this.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic