title: How to think in data stores instead of databases?
body: <p>As an example, Google App Engine uses Google Datastore, not a standard database, to store data.  Does anybody have any tips for using Google Datastore 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 Google Datastore (e.g. performance and the ability to distribute data), but some good database functionality is sacrificed (e.g. joins).</p>
  
  <p>Does anybody who has worked with Google Datastore or BigTable have any good advice to working with them?</p>