Live data from Hacker News

Databases in 2021: A Year in Review

ottertune.com

61–70 of 136 posts

Re: Databases in 2021: A Year in Review

#61

I wish there was some API that abstracted the DB and all technical details and you could connect nodes to it that are specific databases with specific capabilities and it would delegate as necessary.

You're basically talking about Airflow/Airbyte/custom ETL + database expertise. The only way to get efficient performance is expertise, expertise is expensive, ETLs are a given when you have expertise... Just hire a DB consultant or two and you're all set.

Re: Databases in 2021: A Year in Review

#62

Databases in 2030: SQL DB finally succumbs to Graph DB as #1 Does anyone else feel like a caveman when modeling a many to many relationship in a normalized schema, and then querying via SQL? I’m surprised graph DBs aren’t more popular for this reason alone. Maybe it’s a far fetched dream, but perhaps a graph frontend can be slapped onto the Postgres backend.

Relational data schemas are a graph

Re: Databases in 2021: A Year in Review

#63

Databases in 2030: SQL DB finally succumbs to Graph DB as #1 Does anyone else feel like a caveman when modeling a many to many relationship in a normalized schema, and then querying via SQL? I’m surprised graph DBs aren’t more popular for this reason alone. Maybe it’s a far fetched dream, but perhaps a graph frontend can be slapped onto the Postgres backend.

I’ll take Hasura for 500

Re: Databases in 2021: A Year in Review

#64
post #31
post #4

Postgres's dominance is well deserved, of course. My only concerns with it, both are actively worked on, are bloat management (significant for update heavy workloads and programmers used to the MySQL model of rollback segments) and the scaling of concurrency (going over 500 connections). Bloat was taken over by Cybertec[1] after stalling for a bit and is funded (yay), while concurrency was also enhanced out of Micros…

Another concern, no temporal tables, don't businesses demand this feature?

What do temporal tables do that good queries don't?

Re: Databases in 2021: A Year in Review

#65
post #32

I genuinely couldn't tell if the author was being sarcastic when he said Larry Ellison was down on his luck because he dropped from 5th richest to 10th richest (and the whole thing about pulling himself out of the gutters by clawing up to 5th richest again).

Seems like he's being serious and based on the linked tweet, I think he reveres Larry Ellison.

Re: Databases in 2021: A Year in Review

#66
post #11

Earlier quoted context omitted.

Couple of points: 1. Ottertune doesn't sell PostgreSQL services, they sell a database optimization service that happens to support PostgreSQL (and other databases like MySQL) 2. PostgreSQL is definitely gaining market shares and fast, see the db-engine graph [1], you can compare it to the oracle trend if you are not convinced [2] [1] https://db-engines.com/en/ranking_trend/system/PostgreSQL [2] https://db-engines.com…

Is this ranking by # of orgs using Postgres, or relative total company value using Postgres, or some even more ambiguous effectiveness metric? Answer: https://db-engines.com/en/ranking_definition

A DB system that works for professionals and doesn't require any public ecosystem of training materials won't be mentioned much in public.

Re: Databases in 2021: A Year in Review

#70
post #32

I genuinely couldn't tell if the author was being sarcastic when he said Larry Ellison was down on his luck because he dropped from 5th richest to 10th richest (and the whole thing about pulling himself out of the gutters by clawing up to 5th richest again).

It obviously was sarcastic.
Post reply on HN