---
title: "Discussion on \"Cloud SQL vs AlloyDB vs Firestore: Picking the Right Database on GCP\" | Hashnode"
description: "Discussion on \"Cloud SQL vs AlloyDB vs Firestore: Picking the Right Database on GCP\". Almost always Cloud SQL — here's why, when AlloyDB earns its cost, and the cases where Firestore is genuinely the right choice"
url: "https://hashnode.com/posts/cloud-sql-vs-alloydb-vs-firestore-picking-the-right-database-on-gcp/6ae4142b19ee98b16a7439c5"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Cloud SQL vs AlloyDB vs Firestore: Picking the Right Database on GCP](https://blog.madhav.dev/cloud-sql-vs-alloydb-vs-firestore-picking-the-right-database-on-gcp?utm_source=hashnode&utm_medium=feed)

Almost always Cloud SQL — here's why, when AlloyDB earns its cost, and the cases where Firestore is genuinely the right choice

Oct 30 · 6 min read · blog.madhav.dev  
Read the article

-   [#gcp](https://hashnode.com/tag/gcp)
-   [#cloud-sql](https://hashnode.com/tag/cloud-sql)
-   [#alloydb](https://hashnode.com/tag/alloydb)
-   [#firestore](https://hashnode.com/tag/firestore)
-   [#postgresql](https://hashnode.com/tag/postgresql)
-   [#database](https://hashnode.com/tag/database)
-   [#cloud-architecture](https://hashnode.com/tag/cloud-architecture)

## Written by

[Madhav Bhasin](https://hashnode.com/@madhavbhasin)

@madhavbhasin · Noida, India

  
[View profile](https://hashnode.com/@madhavbhasin)

Production patterns for backend engineers who are tired of hello-world tutorials.

Senior full-stack engineer and engineering lead with 5+ years building cloud-native systems at scale. I write about the things the docs don't cover — GCP, FastAPI, Terraform, event-driven architecture, and AI-powered backends. No hello-world demos.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
