Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
  • 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 all forums
this forum made possible by our volunteer staff, including ...
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
  • Paul Clapham
  • Junilu Lacar
  • Knute Snortum
Saloon Keepers:
  • Ron McLeod
  • Ganesh Patekar
  • Tim Moores
  • Pete Letkeman
  • Stephan van Hulst
  • Carey Brown
  • Tim Holloway
  • Joe Ess

Design Approach  RSS feed

Ranch Hand
Posts: 34
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,

I am in a confusion what could be the better design approach.


I am currenly connected to a legacy system which is a primary, now I need to migrate to oracle (secondary)...but don't want to shutdown my primary DB immedietly which will become secondary after the migration...for this what is the correct solution in terms of solution archiecture... Want to maintain both primary and secondary for some time.

Posts: 21
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Chenna,

I'd suggest to have all datasource (I assume legacy is kind of datasource) migration scripts ready and tested. Copy data over and connect both datasources to your system. Next try to keep updating (update, create, delete operations) both datasources, but proceed all read operations from original datasource. After a while check consistency of data in the second datasource and if it looks OK try to switch to it (but keep updating the legacy to make sure that you can always come back in case of any probs).

It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!