This lab walks you through Google Cloud SQL and its features.
You will be creating a Database Instance initially.
Secondly, you will create your Database.
Finally, you will create your tables and insert data into the table.
Region: us-central1 , Zone: us-central1-a
Duration: 45 minutes
Google Cloud SQL is a relational database service where its main offerings are relational data, transactional data (mainly used in banks). For e.g. Without database transactions your bank would not offer you to transfer money from one account to another, What if the transfer of $100 didn't result in receiving in destination account, your bank just lost $100. That's why SQL is required. It has features like commit or rollback.
A classic relational database has a lot of setup required, management, Configuration, maintenance, administer, to get rid of all these. GCP provides you a platform where one can easily manage or administer your database instances.
It offers MySQL, PostgreSQL, SQL Server as a fully managed service, it offers a database that is capable of handling terabytes of data (up to 30 TB). You always have an option of running your own DB server in VM machine but then you have management overhead.
It provides read replica, external replica, failover features, if there is an outage, it will failover to another zone
Backup option is there, either scheduled or on-demand
You can scale vertically by changing machine type or horizontally like Read replica
Customer data is always encrypted where on google internal network or in DB tables, or in the backup.
Cloud SQL is compatible with other Google services like app engine, compute engine, or external applications also like MySQL workbench.
It reduces maintenance costs and automates Database provisioning, backups, patches, capacity increases ensuring 99.95% availabilty.
It provides you High Availability with automatic failover.
Data is always encrypted at rest or in transit
It helps you focus on your app rather than management.
The primary instance writes logs to the system database every second in terms of the heartbeat signal, in any case, if heartbeats aren't detected for 60 seconds, a failover process is initiated. This may also occur if the zone containing the primary instance experiences an outage. In case of failover, the standby instance serves as a backup database from the secondary zone.
Starting Cloud Shell.
Creating a Database instance.
Creating a MySQL Database.
Creating a table in your database.
Inserting data into your table.