Recently, Google has launched the Second Generation instances for Cloud Sequel service with new features.
This article will cover information about a single service in the Google Cloud Platform, Google Cloud SQL.
What is Google Cloud SQL as a managed service?
Google Cloud SQL is a managed database service. By that we mean Google Cloud SQL aims to offload the mundane tasks associated with database management making no mistake. It is not a DBA replacement. It doesn’t do query optimization for you. For example, in terms of management, Cloud SQL offers my sequel and as of last month the Postgres as well. These databases, google is not offering my sequel compatibility or Postgres compatibility. They are offering as close to vanilla Community Edition my sequel as they can and similarly as close to vanilla Postgres. So what this means is if your application works with my sequel or it works with post Postgres, it should work with Google Cloud SQL.
Google Cloud SQL is one of GCP products
Most everybody used a managed database service like cloud sequel or Amazon RDS or as own sequel or Heroku. Therefore, google has got a kind of a mix looks like some folks doing both. A managed service will take care of plumbing for you. For instance, cloud sequel can post your logs pretty easily to pub/sub which has a tie-in to Splunk As, an example when you’re in the self-managed world. If you do that plumbing yourself, you need to figure how to get those logs to something else that you want to consume.
Infrastructure scaling up is always kind of the the most intuitive thing showing how to select number of CPUs and RAM based on the machine type that you picked. You can always change those on the Cloud SQL instance. The thing to note here is that when you change those you do incur downtime, Google has to reboot the VM. Google put you in a different VM which means you’re down for about three minutes. Hence, if you want to change Ram CPU you’re going to take about three minutes down when you want to change storage performance. If you’re adding more capacity, you have to take your database down.
Google cloud sql has a scalability performance
Google Cloud SQL has a performance calculator in in the product itself. These numbers are going to be stale in the near future. At some point, surely, you will say that it’s nice to run on one big database but you have got a workload now. It demands you to scale out at least your reads. If you want to do that in Cloud SQL, it’s fairly quick to do. Since Google Cloud SQL does offer read replicas. You saw kind of what the UI looks like Google can quickly add one or more read replicas to the master rakonin instance.
Like Amazon AWS, Google provides us with a very full virtualization ecosystem that virtualises everything from PCs, switches, routers, firewalls … VPS (Cloud Computing) is just a tiny part of the system. This ecology with the internet speed going up in just a few years, you will no longer see the computer case. We’ll all be working on the cloud with just a screen and keyboard.
In conclusion, Google Cloud SQL is a huge commercial data repository built to handle problem with fast SQL queries. Thanks to it, storage and retrieval problem on large databases due to the lack of appropriate hardware and infrastructure is now solved.