Live data from Hacker News

Databases in 2024: A Year in Review

cs.cmu.edu

91–100 of 220 posts

Re: Databases in 2024: A Year in Review

#91

Redis is slow?

I wish there was more context around that statement in his post.

Redis while not having some of the features he mentions in [1] (i.e. SQL), when used for what it excels at is usually not considered "slow".

As an in-memory data structure server, a common use case is to use it for where some operations in a typical RDBMS are slow.

[1] https://youtu.be/fZbwD1gzjLk?t=2018

Re: Databases in 2024: A Year in Review

#93
post #69
post #66

Earlier quoted context omitted.

> Wow, the reasons why Redis commands API suck in Andy's video (linked in the post) are the weakest ever. In my example, the API on a key changes based on its value type. And the same collection can have different value types mixed together. You've recreated the worst parts of IBM IMS from the 1960s. However, the original version of IMS only changed the API when a collection's backing data structure changed. Redis ca…

You totally miss that Redis is more like a remote interpreter with a DSL that manipulates data structures stored at global variables (keys): you (hopefully) would never complain about languages having this semantics. I don't think you understood how Redis collections work. The items are just strings, they can't be mixed like integers or strings together or whatever, nor collections can be nested. The Redis commands d…

Just because there are reasons for why Redis sucks doesn’t meant it doesn’t suck

Re: Databases in 2024: A Year in Review

#94
post #45

Weird how SQL Server and its Azure variants gets no mention. It dominates in certain sectors. DBEngines ranks it third most popular overall https://db-engines.com/en/ranking

Are people choosing SQL Server independently of the Microsoft ecosystem? My understating is that you typically use it because you’re forced to choose a MS product.

Agreed with the other person. It's a great database. I wouldn't choose it for a startup over Postgres, but it is extremely capable.

Re: Databases in 2024: A Year in Review

#95
"I've never met anybody that used Alteryx"

I have! It's a pretty good no-code/minimal-code graphical ELT+Analytics in one tool. It's one of those alternate-universe tools that has it's own way of doing things from everything else in the industry, but it’s pragmatic and the people who use it tend to love it.

The one thing that makes it viable is that is has/had (pre-acquisition) very aggressive compatibility with anything else that can hold data, so you can use it as a bolt-on to whatever other databases or files your company has.

Despite what the PE press release about the acquisition says, it has virtually nothing to do with AI, at lease in the modern big NN sense.

If you're looking to fix your giant pile of alteryx workbooks or migrate them to something else, hmu

Re: Databases in 2024: A Year in Review

#96
post #69
post #66

Earlier quoted context omitted.

> Wow, the reasons why Redis commands API suck in Andy's video (linked in the post) are the weakest ever. In my example, the API on a key changes based on its value type. And the same collection can have different value types mixed together. You've recreated the worst parts of IBM IMS from the 1960s. However, the original version of IMS only changed the API when a collection's backing data structure changed. Redis ca…

You totally miss that Redis is more like a remote interpreter with a DSL that manipulates data structures stored at global variables (keys): you (hopefully) would never complain about languages having this semantics. I don't think you understood how Redis collections work. The items are just strings, they can't be mixed like integers or strings together or whatever, nor collections can be nested. The Redis commands d…

>> stored at global variables

This is an interesting (and correct) perspective. Global variables scare us in software but we are ok with it when it comes to application state stored in a db.

Re: Databases in 2024: A Year in Review

#98

Pretty funny. One factual issue: "The university had previously announced that this player was transferring from Louisiana State to Michigan." This is not true. Underwood had committed to LSU but then switched his commitment to Michigan. He was still in high school at the time, and has never attended LSU. But, do you really expect a funny database prof to know much about football?

I never thought I’d see a discussion about the Underwood NIL drama on a databases blog post but here we are.

Re: Databases in 2024: A Year in Review

#99

I love SQL. I'm not a full-time developer but always use SQL over other abstractions, which I find extremely confusing and way more complicated that plain SQL.

That's just because it is what you are comfortable with. Many developers will jump straight for ORMs when given the chance.

Which for certain types of applications ORMs absolutely have their use.

Re: Databases in 2024: A Year in Review

#100
post #87

Earlier quoted context omitted.

> It's boring database engine that powers boring business applications I'm taking that as a positive thing... it's boring and does its job with little fanfare. That's pretty much what I want out of a RDBMS. So long as it is "fast-enough" with enough features for the applications that use it, that seems like a good place for an RDBMS to be. One could still argue about Windows and licensing fees, but from a technical p…

There’s other boring databases that also reliably fill that job, and they also cost far less. It can also be a bit of a pain outside the C# ecosystem, whereas every language ever has nice postgres drivers that don’t require us to download arms setup ODBC. It runs on Linux as of a few years ago, but I also wouldn’t be surprised if many people didn’t realise that.

I’ve run into MSSQL on Linux. Most DBAs know but their entire ecosystem is Windows Server so what’s another Windows Server is their thinking.
Post reply on HN