Databases in 2021: A Year in Review • Hacker News Board

Re: Databases in 2021: A Year in Review

#81

Post by tpetry » Thu, Dec 30, 2021, 9:47 AM UTC

czhu12 wrote: post #33

It's weird to put postgres into the same bucket as elastic search as they are often used for different things. No matter how much you tune / denormalize postgres, you'll never get the free text search performance elastic search offers. Our best efforts on a 5 million row table yielded 600ms query times vs 30-60ms. Similarity with snow flake, you'd never expect postgres to perform analytical queries at that scale. I k…

The author is talking about a different classes of rdbms. I believe his intention was not to compare PostgreSQL to ElasticSearch or ClickHouse which will solve a completely different problem.

But for small to medium datasets his advice to just stick to PostgreSQL is good: Start with an easy solution which will give you anything you need (by simply installing a plugin). If you need more specialized software THEN use it, but don't start with an overcomplicated stack because ElasticSearch and ClickHouse may be the state-of-the-art open source solution to a specific problem.

Re: Databases in 2021: A Year in Review

#82

Post by tpetry » Thu, Dec 30, 2021, 9:49 AM UTC

cloudengineer94 wrote: post #77

Postgress is amazing, however I work with SAP HANA every day and I gotta say this thing is completely insane.

Can you share some information about SAP HANA? Why is it insane? Insanely good or bad? I have no experience with it.

Re: Databases in 2021: A Year in Review

#83

Post by ttiurani » Thu, Dec 30, 2021, 10:15 AM UTC

> Databases Are the Most Important Thing in My Life After My Family > I even broke up with a girlfriend once because of sloppy benchmark results.

I can't say I can relate, but I do appreciate being this passionate about things!

Re: Databases in 2021: A Year in Review

#84

Post by ransom1538 » Thu, Dec 30, 2021, 10:23 AM UTC

I am so confused. https://vitess.io/ I would check this page out and view it's "Who uses Vitess" section. Postgres is awesome if you are running a stand alone server with 300 users or creating the next "uber for cats". But at scale mysql has all the solutions. DBs are not js frameworks.

Re: Databases in 2021: A Year in Review

#85

Post by ransom1538 » Thu, Dec 30, 2021, 10:29 AM UTC

hu3 wrote: post #6

I expected more mentions of Vitess, which honestly looks like some kind of alien black magic from what I saw while consulting for a client this year. But I guess not much else happened to it other than PlanetScale.

All major companies are moving to Vitess. The battle is over. No one at scale uses Postgres.

Re: Databases in 2021: A Year in Review

#86

Post by code_biologist » Thu, Dec 30, 2021, 11:05 AM UTC

newlisp wrote: post #31

why-el wrote: 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?

Would love to see wider support for temporal tables, but application level approaches like https://github.com/jazzband/django-simple-history have worked for the business issues I have.

Re: Databases in 2021: A Year in Review

#87

Post by code_biologist » Thu, Dec 30, 2021, 11:12 AM UTC

manigandham wrote: post #51

newlisp wrote: post #31

Earlier quoted context omitted.

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

I've never seen a business actually use them, large or small. Any auditing requirements are usually fed from other sources, like Kafka event streams, files on S3, or a OLAP data warehouse.

How do you set up and feed the warehouse? Temporal-ish tables have been an obvious, simple, and mostly foolproof solution for many of our historical analytics and reporting needs.

Bitemporal stuff (enabling edited versions of history) is where things get hairy and I definitely question the utility outside of a dedicated use case.

Re: Databases in 2021: A Year in Review

#88

Post by code_biologist » Thu, Dec 30, 2021, 11:16 AM UTC

czhu12 wrote: post #33

It's weird to put postgres into the same bucket as elastic search as they are often used for different things. No matter how much you tune / denormalize postgres, you'll never get the free text search performance elastic search offers. Our best efforts on a 5 million row table yielded 600ms query times vs 30-60ms. Similarity with snow flake, you'd never expect postgres to perform analytical queries at that scale. I k…

Not affiliated, but for anyone looking to do searches on data stored primarily in Postgres via Elastic, ZomboDB is pretty slick.

ZomboDB is a Postgres extension that enables efficient full-text searching via the use of indexes backed by Elasticsearch. https://github.com/zombodb/zombodb#readme

Re: Databases in 2021: A Year in Review

#89

Post by eurasiantiger » Thu, Dec 30, 2021, 11:56 AM UTC

srcreigh wrote: post #62

criticaltinker wrote: post #22

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

And exactly for that reason, graph DBs can be more intuitive to work with: relational DBMSs generally don’t support any kind of graph operations or traversal queries.

Re: Databases in 2021: A Year in Review

#90

Post by _the_inflator » Thu, Dec 30, 2021, 12:01 PM UTC

zffr wrote: post #29

The author is a professor at CMU who specializes in databases: https://www.cs.cmu.edu/~pavlo/ Not completely related, but his lectures on databases on YouTube are really good. Much better than the DB class I had at college.

The author is hilarious! Quote from his article: “I even broke up with a girlfriend once because of sloppy benchmark results.”