relational

The problem is people shoehorning relational problems into non relational databases.

Basically as you scale relational databases, you end up sharding and loose a lot of the relational features, and basically end up with NoSQL.

You might see smaller federated data marts or even separately managed relational dbs all over the place.

Especially if you're interested in low-lever relational db stuff - how SQL statements are processed, data is stored, B-Trees, etc.

Though a lot of the youngsters these days don't seem to bother with relational databases.

Strong Database querying skills and knowledge of both relational and key value storage models.

You can go really far with most relational database engines by adding hardware to a single instance instead of adding more instances.

Another thing to consider that I don't see covered often is the object relational nature of PostgreSQL.

Leave your relational data for the database and use something more efficient!

We use it in production, but are migrating away from it for some projects since that data is better suited for a relational DB.

Versus implementing bloom filters in a relational database?

> separately managed relational dbs all over the place On the BI side, this is overwhelmingly the outcome for large companies.

When I first heard of statmuse I had your same question, best I could come up with is "Constructing an Interactive Natural Language Interface for Relational Databases"[1].

Relational algebra is beautiful and elegant, but SQL is a dated, '70s-y syntax on top of that.

Relational Databases are nice, but I would rather deal in objects (well frames).