Skip to main content

Command Palette

Search for a command to run...

SQL and NoSQL – A “Wow” Moment from a SQL Mindset

Updated
2 min read
SQL and NoSQL – A “Wow” Moment from a SQL Mindset

I am a SQL resource through and through.

For years, I thought in tables, joins, fact–dimension models, indexes, partitions, and materialized views. When I first started designing collections in Google Cloud Firestore, I instinctively modeled them like SQL — helper collections, mapping layers, strict normalization.

Only later did I realize:

I wasn’t even using half of what Firestore was capable of.

That was my “wow” moment with NoSQL.


SQL: Structured, Analytical, Powerful

In relational systems like PostgreSQL or warehouses such as Snowflake, we design for:

  • Referential integrity

  • Normalization to reduce redundancy

  • Complex joins

  • Aggregations and reporting

  • Indexing and partitioning strategies

SQL shines when reporting and analytics are the primary goal.

The core mindset:

Store data cleanly. Join it later.


NoSQL: Model for How You Read

Document databases shift the thinking entirely.

There are no joins. Instead:

  • Documents are shaped exactly like your application needs them.

  • Queries are index-driven, and commonly queried fields are automatically indexed.

  • You design around access patterns.

We don’t normalize for relational joins. Instead, we structure documents around how they will be retrieved.

In SQL, redundancy is usually avoided.
In NoSQL, controlled duplication can improve performance.

The mindset becomes:

Store data the way you read it.


SQL vs NoSQL — A Practical Comparison

Aspect

SQL

NoSQL (Document DB)

Primary Use Case

Reporting, analytics

Web/mobile applications

Data Model

Tables with relations

Documents & collections

Joins

Supported and powerful

Not supported

Normalization

Strongly encouraged

Often denormalized intentionally

Schema

Fixed / structured

Flexible / evolving

Optimization Goal

Query flexibility

Low-latency reads

Typical Workload

OLAP

OLTP


Final Reflection

SQL and NoSQL are not competitors. They solve different problems.

SQL is ideal for analytical depth.
NoSQL is ideal for operational speed.

As someone trained in star schemas and joins, learning NoSQL felt like unlearning discipline.

But it isn’t less disciplined.

It’s a different kind of discipline.

And that was my real “wow” moment.