Google Cloud SQL & AWS RDS

Google Cloud SQL & AWS RDS

Here is a quick recap of the main functionalities of both products:


Functionality
AWS RDS
Cloud SQL
CPU & RAM 
RDS supports three types of instance classes: Standard, Memory Optimized, and Burstable Performance. 
Cloud SQL is divided into shared-core, standard and high memory machines. 
Types of Storage
General Purpose SSD, Provioned IOPS (SSD) and Magnetic
Supports both SSD and HDD (magnetic)
IOPS ratio (SSD)
General Purpose (SSD) has the ability to burst to 3,000 IOPS for extended periods of time. Baseline performance for these volumes is determined by the volume's size. Baseline is 3 IOPS per GiB.
SSD provides IOPS gurantee in a 30:1 ratio. The included 100-GB gurantees for 3000 IOPS. SSDs are preferred over HDD, as it provides lower latency and higher data throughput.
Scaling options
Allocated storage can be scaled or converted to another storage type (General SSD to PIOPS SSD). During the scaling process, the DB instance is available for use but might experience performance degradation.
Automatic storage increase can be enabled in cloud SQL. This automatically increases the storage, if the allocated storage is filled. Storage scaling does not cause any downtime.
Failover Possible
 YES
YES
Jargon
It is called Multi-AZ deployment. Deploys the stand-by instance to a different availability zone in the same region.
Failover Replica. This replica is placed in a different zone within the same region.
Replication Technology
The primary DB instance is synchronously replicated across Availability Zones to a standby replica to provide data redundancy, eliminate I/O freezes, and minimize latency spikes during system backups.
Semi-Synchronous replication is implemented. This is better than synchronous replication in AWS & Azure. To understand the various types of replication, refer https://goo.gl/2CW2st. Stand-by instance is required.
Advantages
RDS instances switches to stand-by during palnned maintenance, software patches which ensures no downtime during system maintenance.
Failover replica can be used as read replica. Semi-Synchronous is better than synchronous replication as the performance impact/cost is greater in the later.
Dis-Advanatages
DB instances using Multi-AZ deployments may have increased write and commit latency compared to a Single-AZ deployment, due to the synchronous data replication that occurs.
Performance impact due to semi-synchronous replication, but better than the AWS & Azure's counterparts.
Cross-Region read replica (Useful for Global scale out, Disaster recovery, migration)
Possible
Not Possible
Max.No.of Read replicas
 5
Not mentioned
High Availabilty of Read Replica (Deploying a standBy replica in a different zone)
 Possible. This is independent of Master DB instance's high availability.
No High availability for read replica
Manual Backup (DB snapshots can be created anytime manually)
Possible
Possible
Applicable Backup Retention Period
1 to 35 days
Life-time of DB. (Doubtful though, I could not find any resource to prove this point)
Advantages
Free backup storage up to the size of the database. For eg: 100 GB of database storage/M, will provide 100 GB/M of backup storage at no additional charge.
Backup retention period is life-time (Not sure, though)

Comments

Post a Comment

Popular posts from this blog

AWS Auto AMI(Instance) backup across all region

Simple Easy to AWS auto AMI backup across all region or cross region using lambda (node js) Click Here For Code Getting Started These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system. Prerequisites What things you need to install the software AWS Lambda AWS Sdk Click Here For Code Installing A step by step series of examples that tell you how to get a development env running Make Policy Using File iam-policy.json Make Role Using File role-trust-policy.json Assign or attach policy to Role Create Two 2 New Lambda Function And Assign Role That you made Use Code From File for Lambda Functions 1. Create_AMI.js 2. Delete_AMI.js Running the tests Run Lambda Function And Check For Snap Shot and AMI Full Automation Using Cloud Watch Use Cloud Watch Event as Trigger To Make Full Automation of Backup System From
Read more

Digital-ocean-auto volume backup

For Code Click Here ...! https://github.com/harsh4870/Digital-ocean-auto-volume-backup Digital ocean auto volume backup shell script.Currently, it will keep 2 newest snapshots. If you want to config this, change the value. What does this script do ? Since DigitalOcean currently didn't provide auto backup for the volume. So, i created the script to call DigitalOcean API and creating volume's snapshot. After successfully created, it will delete the old snapshot. Currently, it will keep 2 newest snapshots. If you want to config this, change the value. Digital ocean API documentation :  https://developers.digitalocean.com/documentation/v2/#introduction Dependency ./jq library Download from :  https://stedolan.github.io/jq/ Linux : sudo apt-get install jq Script use : Config your parameter in snapshot.sh Set cronjob to execute snapshot.sh Parameter : DIGITALOCEAN_TOKEN VOLUME_ID VOLUME_NAME SNAPSHOT_NAME DATE List Down all volumes without jq
Read more

How to Set Up an Nginx Ingress with Cert-Manager on DigitalOcean Kubernetes

Introduction Kubernetes  Ingresses  allow you to flexibly route traffic from outside your Kubernetes cluster to Services inside of your cluster. This is accomplished using Ingress  Resources , which define rules for routing HTTP and HTTPS traffic to Kubernetes Services, and Ingress  Controllers , which implement the rules by load balancing traffic and routing it to the appropriate backend Services. Popular Ingress Controllers include  Nginx ,  Contour ,  HAProxy , and  Traefik . Ingresses provide a more efficient and flexible alternative to setting up multiple LoadBalancer services, each of which uses its own dedicated Load Balancer. In this guide, we'll set up the Kubernetes-maintained  Nginx Ingress Controller , and create some Ingress Resources to route traffic to several dummy backend services. Once we've set up the Ingress, we'll install  cert-manager  into our cluster to manage and provision TLS certificates for encrypting HTTP traffic to the Ingress. Prereq
Read more