Skip to content

mateusstp/gcp-certifications

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

12 Commits
 
 
 
 
 
 

Repository files navigation

Learn About GCP Certifications

This project is designed to help you learn about Google Cloud Platform (GCP) certifications. It provides resources, study guides, and practice questions to prepare for various GCP certification exams. Whether you're a beginner or an experienced professional, this project aims to support your journey in achieving GCP certifications.

AlloyDB vs. Spanner

AlloyDB

AlloyDB is a managed database service designed for high-performance transactional workloads. It combines the best of PostgreSQL with Google's infrastructure, offering enhanced performance, scalability, and availability. AlloyDB is ideal for applications requiring strong consistency and low-latency transactions.

Key Points:

  • PostgreSQL-compatible: Ensures seamless migration and integration with existing PostgreSQL applications.
  • Optimized for transactional workloads: Provides high performance for applications requiring fast and reliable transactions.
  • Automatic scaling: Scales resources automatically to handle varying workloads.
  • Built-in security features: Includes advanced security features to protect sensitive data.

Objectives:

  • Enhance transactional performance: Deliver significantly faster transaction processing compared to standard PostgreSQL.
  • Simplify database management: Automate routine tasks such as backups, patching, and upgrades.
  • Reduce operational costs: Optimize resource utilization and minimize administrative overhead.

Spanner

Spanner is a globally distributed database service that provides strong consistency, horizontal scalability, and high availability. It is designed for applications that need to scale across regions and handle large volumes of data with minimal latency. Spanner is suitable for use cases requiring both high availability and strong consistency on a global scale.

Key Points:

  • Globally distributed: Provides data replication across multiple regions for high availability and low latency.
  • Strong consistency: Ensures that all reads return the most recent committed data, regardless of location.
  • Horizontal scalability: Scales seamlessly to handle massive amounts of data and traffic.
  • Automatic data management: Automates data distribution, replication, and recovery.

Objectives:

  • Provide global scalability: Enable applications to scale across geographical regions without compromising performance.
  • Ensure strong data consistency: Guarantee data integrity and consistency across all replicas.
  • Minimize downtime: Offer high availability with automatic failover and recovery mechanisms.
  • Simplify global data management: Automate complex tasks associated with managing a globally distributed database.

Labs Summary

AlloyDB

  • challenge_alloyDB.sh: A shell script likely related to a challenge or lab exercise involving AlloyDB.

Spanner

  • 01_fundamentals.sh: A shell script covering the fundamentals of Spanner.
  • 02_loadinf_data.sh: A shell script for loading data into Spanner.
  • 03_schemas_and_queires.sh: A shell script focusing on schemas and queries in Spanner.
  • 04_webapp_and_spanner.sh: A shell script involving a web application and its integration with Spanner.
  • batch_insert.py: A Python script likely for batch inserting data into Spanner.
  • challenge: A directory containing additional challenge-related content.
  • environment.ts: A TypeScript file, possibly for environment configuration.
  • insert.py: A Python script for inserting data into Spanner.
  • requirements.txt: A file listing Python dependencies for the Spanner labs.
  • snippets.py: A Python script containing code snippets related to Spanner.
  • spanner.tf: A Terraform script, potentially for provisioning Spanner resources.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors