Book Image

Google Cloud Platform for Architects

By : Vitthal Srinivasan, Loonycorn , Judy Raj
Book Image

Google Cloud Platform for Architects

By: Vitthal Srinivasan, Loonycorn , Judy Raj

Overview of this book

Using a public cloud platform was considered risky a decade ago, and unconventional even just a few years ago. Today, however, use of the public cloud is completely mainstream - the norm, rather than the exception. Several leading technology firms, including Google, have built sophisticated cloud platforms, and are locked in a fierce competition for market share. The main goal of this book is to enable you to get the best out of the GCP, and to use it with confidence and competence. You will learn why cloud architectures take the forms that they do, and this will help you become a skilled high-level cloud architect. You will also learn how individual cloud services are configured and used, so that you are never intimidated at having to build it yourself. You will also learn the right way and the right situation in which to use the important GCP services. By the end of this book, you will be able to make the most out of Google Cloud Platform design.
Table of Contents (19 chapters)
13
Logging and Monitoring

Working with Datastore

In this section, we will understand the ideal set of circumstances that should warrant the use of Cloud Datastore, when not to use Datastore, and the ideal design choices to make when using Datastore.

When to use Datastore

Here is a list of scenarios where you probably shouldn't choose Datastore as your storage option:

  • Don't use Datastore if you need very strong transaction support. If you are doing hardcore OLTP, you should use something like Cloud Spanner.
  • If you want basic ACID support, Datastore is probably enough for you.
  • Datastore works best when data is hierarchical and highly structured. If you have data which is non-hierarchical or unstructured, Bigtable is probably a better NoSQL...