News for hackers. Stuff that matters.
Re:Databases in 2024: A Year in Review by tayo42 on Wednesday January 01, 2025 @01:47PM (#42568117)
> Andy's video (linked in the post)

Is there a "to long didnt watch" summary any one knows of? I hate videos, but am curious lol

Re:Databases in 2024: A Year in Review by jghn on Wednesday January 01, 2025 @07:41PM (#42570570)
Right there with you. The trend towards video content instead of written sucks so much.
Re:Databases in 2024: A Year in Review by samanthasu on Wednesday January 01, 2025 @09:12PM (#42571005)
same same
Re:Databases in 2024: A Year in Review by nodamage on Thursday January 02, 2025 @03:21AM (#42572707)
As far as I can tell the two main criticisms in the video are that:

1. The Redis API requires the developer to use different commands to retrieve/manipulate data depending on the type of data being stored. To retrieve a string you use GET, but if you want to retrieve a list it's LRANGE, for a set it's SMEMBERS, for a hash it's HGETALL. (As opposed to an API design which would allow you to call GET on all of the different data types and have it return the right thing.)

2. The lack of a predefined schema means you can overwrite values with different types. So you can create a list named "foo" and then overwrite it with a string named "foo" and then overwrite that with a hash named "foo" and Redis will happily do it, meaning the developer needs to keep track on their end what actual type any given key is holding onto.

To me these criticisms come across as essentially saying "Redis doesn't behave like a RDBMS" to which I suppose antirez's point is "well, yeah, it's not supposed to".

Re:Databases in 2024: A Year in Review by tayo42 on Thursday January 02, 2025 @12:22PM (#42576380)
thanks for saving me some time!