I think one thing Andy misses about why people were pissed about Elastic and Redis but not as many for MongoDB and some other is their license and size of Contributors Community. When original license is as restricted as AGPL it is unlikely there is much of embedded use... so less people are impacted in truly catastrophic way Also if there is no contributor community to speak of... who is going to do the fork ? I put…
Databases in 2024: A Year in Review
121–130 of 220 posts
Re: Databases in 2024: A Year in Review
#122Earlier quoted context omitted.
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.
SQL Server is a terrific product. And I detest most things Microsoft.
Re: Databases in 2024: A Year in Review
#123Earlier quoted context omitted.
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.
I would use it if it supported backup/restore over unix pipes / ssh.
I used this hack for backing up Oracle 30 years ago.
Something like 'mknod p backup.dmp; oradump .... file=backup; dd if=backup.dmp | ssh othermachine receiver-process'
Re: Databases in 2024: A Year in Review
#124Earlier quoted context omitted.
How do they enforce the ban? Do universities have non-compete clauses for PhD students?
I assume it's not that kind of ban, but more like he'll recommend his students to avoid the company.
Re: Databases in 2024: A Year in Review
#125Weird 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
SRE who deals with some .Net stuff that uses MSSQL but is converting to MySQL. so I feel somewhat qualified to talk about MSSQL. TL;DR: Nothing interesting going on. There is nothing to talk about here. It's boring database engine that powers boring business applications. It's pretty efficient and can scale vertically pretty well. With state of modern hardware, that vertical limit is high enough most people won't enc…
Same thing is happening now to Postgres vs enterprisey DBs.
Re: Databases in 2024: A Year in Review
#126Re: Databases in 2024: A Year in Review
#127Earlier quoted context omitted.
Yes. 1. It is single-threaded, which severely limits throughput for a single instance. 2. All communication must go over a socket, which severely impacts latency for use cases where it could otherwise run in-process.
What is the better alternative?
Re: Databases in 2024: A Year in Review
#128This take screams more than a technical criticism but of something personal. “I'll be blunt: I don't care for Redis. It is slow, it has fake transactions, and its query syntax is a freakshow. Our experiments at CMU found Dragonfly to have much more impressive performance numbers (even with a single CPU core). In my database course, I use the Redis query language as an example of what not to do.” (From the article) Of…
Re: Databases in 2024: A Year in Review
#129Wow, the reasons why Redis commands API suck in Andy's video (linked in the post) are the weakest ever. It is possible to make a case against the Redis API (I would not agree of course but... it's totally legitimate), but you gotta have stronger arguments than those, particularly if you are a teacher of some kind. Especially: you need to be somewhat fluent in Redis and how developers use Redis in order to understand…
> 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
#130Redis is slow?
[0] https://www.microsoft.com/en-us/research/blog/introducing-ga...
[1] https://news.ycombinator.com/item?id=39752504
[2] https://microsoft.github.io/garnet/docs/commands/api-compati...