You had the following situation: you need to store information, but part of this information is well modeled using one type of database (in a very loose sense), and the other part is well modeled with another type. Examples:
- a set of files and additional information about each of them stored in a relational SQL database.
- OODB with a triplester.
- two previously completely unrelated key / value data stores that should be integrated but separated.
What do you think is the best way to deal with this situation? keep separation of the two data types and write a software layer that synchronizes them? use only one type of database, adapting one type of data to another (for example, saving a file in relational db as blob or saving the relational part in a hacked file database on disk)?
source
share