Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Google Cloud Platform for Architects

You're reading from  Google Cloud Platform for Architects

Product type Book
Published in Jun 2018
Publisher Packt
ISBN-13 9781788834308
Pages 372 pages
Edition 1st Edition
Languages
Authors (3):
Vitthal Srinivasan Vitthal Srinivasan
Profile icon Vitthal Srinivasan
Loonycorn Loonycorn
Profile icon Loonycorn
Judy Raj Judy Raj
Profile icon Judy Raj
View More author details
Toc

Table of Contents (19) Chapters close

Preface 1. The Case for Cloud Computing 2. Introduction to Google Cloud Platform 3. Compute Choices – VMs and the Google Compute Engine 4. GKE, App Engine, and Cloud Functions 5. Google Cloud Storage – Fishing in a Bucket 6. Relational Databases 7. NoSQL Databases 8. BigQuery 9. Identity and Access Management 10. Managing Hadoop with Dataproc 11. Load Balancing 12. Networking in GCP 13. Logging and Monitoring 14. Infrastructure Automation 15. Security on the GCP 16. Pricing Considerations 17. Effective Use of the GCP 18. Other Books You May Enjoy

Comparison with traditional databases

In a traditional RDBMS, you have atomic transactions, which is true for Datastore as well. Datastore does support atomic transactions and the ACID properties, mostly due to the need to keep all of the internal indices consistent. Both traditional RDBMS and Datastore make heavy use of indices for fast lookup. But in Datastore, every query makes use of indices, which is far beyond what traditional RDBMS do. Consequently, the query execution time in Datastore is basically independent of the size of the underlying dataset, which is certainly not the case with traditional RDBMSs.

Traditional RDBMS use relational data, that is, rows and columns, but without many hierarchical relationships within those entity relations. Datastore on the other hand is document-oriented, which implies it is optimized for hierarchically structured data such as XML or...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €14.99/month. Cancel anytime