[1] Disclaimer: I wrote a preliminary CouchDB connector for Lucid that'll get released separately with the upcoming 0.9.4 release.
[2] I believe one of the first postgres foreign data wrappers was around Twitter. So you move some API accessing code from an application layer that realistically only your application can talk to, to the DB layer, and now everything that can talk to the DB layer can access the data. (Unless they want it raw, then they'll get it from Twitter.)
Same issue, installed base and connectivity.
Composition, interfaces, abstraction.
The ideas all seem very formative to me. There are a bunch of assumptions, logic gaps, etc. But it's not all bad.
[1] http://cacm.acm.org/magazines/2011/4/106584-a-co-relational-...
Performance has also been very poor (we use Jena SDB). I don't know if poor performance is an implementation problem or an overall weakness.
1) Two databases are semantically very similar. In such a case even if the query language is different porting your application from one to another is trivial, especially if you have a minimal layer of abstraction between your program and you data, things like fetchUser(ID) or alike.
2) If the data model is different, using the same query language does not help at all.
So the question is WHY? :)