How to think in data stores instead of databases?

Question

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). Does anybody who has worked with Google Datastore or BigTable have any good advice to working with them? Select the correct answer from above options

Answer 1

The database is an organized collection of data. Databases help in the storage and manipulation of data. Databases make data management easy. Let's discuss a few examples. Database Management System (DBMS) is a group of programs that enables the users to access databases, manipulate data, reporting/representation of data. The Google Datastore and BigTable are two different things and Google datastore should not be confused with datastore data storage sense. Bigtable is more expensive than BigQuery. BigQuery does have proper joins and RDBMS like SQL language and it is cheaper, why not use big query. That being said, BigQuery does have some limitations, depending on the size of your data you might or might not encounter them. Also, in terms of thinking in terms of datastore, I think the proper statement would have been "thinking in terms of NoSQL databases". There are too many of them available out there these days but when it comes to Google products except google cloud SQL (which is MySQL) everything else is NoSQL.