mongodb - How to achieve database abstraction/independence in NoSQL world -


we looking @ using mongodb our database in our java server-side application. in earlier project using hibernate abstract underlying sql database, switch mysql postgres (for example) without changing application code. (this + hibernate gave apart usual orm feature).
did search similar abstraction layer document-oriented nosql databases, , ended no results !

though mongodb suffices our requirements of today, if better document-oriented nosql db comes 3 years down line, dont want change our application code move new db.

one solution write abstraction layer ourselves (which if left no other option).

but surprised if people coming orm world coded directly onto nosql db interfaces ?! database independence not concern in nosql world ? or achieved other means ?

the reasons there not being many mature database-agnostic orm layers nosql are:

  1. they lot less standardized. sql iso standard. when stick standard, have make little modifications when change underlying database. document-oriented databases, however, have own query languages.

  2. they work fundamentally different. document-oriented databases have own philosophies, strengths, weaknesses , use-cases. storage strategy works on couchdb might inappropriate mongodb. hard use orm mapper can abstract far can find common denominator in api satisfies of these quirks.

  3. they still rather new technology. sofware ecosystem around them still needs few years evolve standard similar sql.

but note while there no solutions database-agnostic orms in document-oriented database world, there plenty of orm wrappers specific databases. didn't mention programming language using, there solutions mainstream languages. preferred on rolling own.


Comments

Popular posts from this blog

blackberry 10 - how to add multiple markers on the google map just by url? -

php - guestbook returning database data to flash -

delphi - Dynamic file type icon -