The course is part of this learning path
Bigtable is an internal Google database system that’s so revolutionary that it kickstarted the NoSQL industry. In the mid 2000’s, Google had a problem. The web indexes behind its search engine had become massive and it took a long time to keep rebuilding them. The company wanted to build a database that could deliver real-time access to petabytes of data. The result was Bigtable.
Google went on to use Bigtable to power many of its other core services, such as Gmail and Google Maps. Finally, in 2015, it made Cloud Bigtable available as a service that its customers could use for their own applications.
In this course, you will learn which of your applications could make use of Bigtable and how to take advantage of its high performance.
- Identify the best use cases for Bigtable
- Describe Bigtable’s architecture and storage model
- Optimize query performance through good schema design
- Configure and monitor a Bigtable cluster
- Send commands to Bigtable
- Data professionals
- People studying for the Google Professional Data Engineer exam
- Database experience
- Google Cloud Platform account (sign up for free trial at https://cloud.google.com/free if you don’t have an account)
The example code is at https://github.com/cloudacademy/cloud-bigtable-examples/tree/master/java/dataproc-wordcount.
Bigtable provides only a basic level of access control, so this is going to be a short video.
You can assign users to one of 3 roles to control their access to Bigtable: reader, user, and admin. The reader role grants read access to data in tables and also to the performance monitoring graphs. The user role grants write access to tables. The admin role grants full access to everything in Bigtable, including the ability to create new instances.
You can only set these roles at the project level, so a reader, for example, can read all of the data in all of the tables in the project. There’s no way to limit a user’s access to specific tables, rows, or columns. This only applies to users with Google Cloud accounts that can access Bigtable directly, though. You can still, of course, limit end-user access any way you want through your application.
To assign one of the 3 roles to a GCP user, you need to go to the IAM page in the console. If Cloud Bigtable doesn’t show up in the list, then you need to enable the Bigtable API. This is all you have to do.
And that’s it for access control.
About the Author
Guy launched his first training website in 1995 and he's been helping people learn IT technologies ever since. He has been a sysadmin, instructor, sales engineer, IT manager, and entrepreneur. In his most recent venture, he founded and led a cloud-based training infrastructure company that provided virtual labs for some of the largest software vendors in the world. Guy’s passion is making complex technology easy to understand. His activities outside of work have included riding an elephant and skydiving (although not at the same time).