How to think in data stores instead of databases?
Posted
by Jim
on Stack Overflow
See other posts from Stack Overflow
or by Jim
Published on 2008-09-19T17:03:11Z
Indexed on
2010/03/15
21:39 UTC
Read the original article
Hit count: 322
As an example, Google App Engine uses data stores, not a database, to store data. Does anybody have any tips for using data stores instead of databases? It seems I've trained my mind to think 100% in object relationships that map directly to table structures, and now it's hard to see anything differently. I can understand some of the benefits of data stores (e.g. performance and the ability to distribute data), but some good database functionality is sacrificed (e.g. joins).
Does anybody who has worked with data stores like BigTable have any good advice to working with them?
© Stack Overflow or respective owner