Live data from Hacker News

Databases in 2024: A Year in Review

cs.cmu.edu

161–170 of 220 posts

Re: Databases in 2024: A Year in Review

#161
thank you for your work andy!

for a moment i got reminded of the rap music in your courses

im glad that tigerbeetle got here, really impressive team they have.

there are a lot of other missing alien technologies i've discovered recently too like quickwit which is like elasticsearch but s3-compatible, and typesense which is like elasticsearch but memory-based

Re: Databases in 2024: A Year in Review

#162
post #45

Earlier 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.

Us it, though? I worked with it tangentially and found it deficient compared to Postgres. Why pay for a product that's worse than the best free product? In the old days there was a question of who to pay for support that was easier to answer for proprietary DBs, but with cloud services that answer is "you already pay your cloud provider".

Re: Databases in 2024: A Year in Review

#164

Earlier quoted context omitted.

Inspect element on https://web.archive.org/web/20240827031455/https://ottertune... For more context: > I'm to sad to announce that @OtterTuneAI is officially dead. Our service is shutdown and we let everyone go today (1mo notice). I can't got into details of what happened but we got screwed over by a PE Postgres company on an acquisition offer. https://x.com/andy_pavlo/status/1801687420330770841

Because that was a little too subtle and I was sufficiently curious: view-source: https://web.archive.org/web/20240827031455/https://ottertune... scroll until you see ASCII art

needed that. https://en.wikipedia.org/wiki/EnterpriseDB note the PE's

Re: Databases in 2024: A Year in Review

#165
> I need to figure out to juice my stats because in September 2024, Wikipedia removed the article about me over not having enough citations.

guys, what are we doing here. this is ridiculous. andy pavlo cannot get an article on wikipedia? have you seen his work?

Re: Databases in 2024: A Year in Review

#166

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.

Some ORMs have weird design issues. Eloquent for example allows you to pull relationships lazily on single objects, so if you're in a loop that'll create a lot of queries. So much for laziness! I'm OK with this ability, but the API shouldn't encourage it by making it trivial.

Re: Databases in 2024: A Year in Review

#167

I spent the past year puzzling over the DB market as well, but I don't feel like I'm much closer to understanding it. It appears that a lot of attention is now directed at the folks doing 100 MB queries, and the high end has moved past everybody's radar. My idea of an exciting product is Ocient, who have skipped over Cloud and gone for hyperscale on-prem hardware. Yellowbrick is also a contender here. I have a lot of…

> There's a crossover point where self-managed is cheaper than cloud

Single data point here: before cloud managed dbs were a thing our smallish startup was running mysql on virtual servers by installing it from the linux package manager. Always worked great, runs without needing manual attention for years at a time once set up, so I've never felt the need to change.

So at least in some cases the crossover point is "right from the start".

Re: Databases in 2024: A Year in Review

#169

Earlier quoted context omitted.

Anyone know what company he may be talking about?

Inspect element on https://web.archive.org/web/20240827031455/https://ottertune... For more context: > I'm to sad to announce that @OtterTuneAI is officially dead. Our service is shutdown and we let everyone go today (1mo notice). I can't got into details of what happened but we got screwed over by a PE Postgres company on an acquisition offer. https://x.com/andy_pavlo/status/1801687420330770841

Oh wow, didnt know pe-postgres-company had any negative rep.

Anyone care to explain how a company can screw another company via a acquisition offer?

Re: Databases in 2024: A Year in Review

#170
post #69

Earlier quoted context omitted.

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.

There have been proposals to have global state in programming languages which function like databases with the advantages of monitoring/persistence/naming etc, but also retain the modularity of local state.

https://www.scattered-thoughts.net/writing/local-state-is-ha...

https://awelonblue.wordpress.com/2012/10/21/local-state-is-p...

Post reply on HN