Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Databases in 2024: A Year in Review

cs.cmu.edu

Post reply on HN
Print view View original

111–120 of 220 posts

Re: Databases in 2024: A Year in Review

#111

Post by Spivak »

pdhborges wrote: post #105
Spivak wrote: post #85

Earlier quoted context omitted.

I understand machines but threads ?! Why introduce IPC overhead on the fastest/easiest way to share data? This is beyond a solved problem and your language probably has multiple ready-made battle tested solutions. In Python you don't even need a lib, dict is thread safe even in nogil.

In Python you don't even need a lib, dict is thread safe even in nogil. Is it? https://google.github.io/styleguide/pyguide.html#218-threadi...

Yep! Not every operation you can do on a dict is thread safe but if you find a situation where it isn't it's a bug.

https://github.com/python/cpython/issues/112075

Google is recommending people not rely on it because it does make dict subclasses not substitutable. It's easy enough to avoid the issue completely so in most cases you might as well do that.

Re: Databases in 2024: A Year in Review

#112

Post by senderista »

spprashant wrote: post #51
mebcitto wrote: post #29

A couple of spicy things: > OtterTune. Dana, Bohan, and I worked on this research project and startup for almost a decade. And now it is dead. I am disappointed at how a particular company treated us at the end, so they are forever banned from recruiting CMU-DB students. They know who they are and what they did. Ouch. > Lastly, I want to give a shout-out to ByteBase for their article Database Tools in 2024: A Year in…

Anyone know what company he may be talking about?

Well, there's a leading Postgres company which is owned by not one but two PE firms...

Re: Databases in 2024: A Year in Review

#113

Post by yencabulator »

C-programmer wrote: post #109
spprashant wrote: post #51

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

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

Re: Databases in 2024: A Year in Review

#116

Post by senderista »

softwaredoug wrote: post #34

On the “Amazon can just offer your DB as a service” Yes this can happen. But a lot of people don’t want a AWS managed service. They're like 30% cheaper for 30% less value. They can develop a bad reputation and feel like weird forks (kinesis vs Kafka) that have weird undocumented gotchas and edge cases that never get fixed. Many teams want to host on k8s anyway, and you’ll probably have better k8s support from the mai…

Kinesis is not Kafka (at all), nor is Google Dataflow Flink (perhaps you're thinking of Apache Beam?).

Re: Databases in 2024: A Year in Review

#117

Post by didgetmaster »

ak_111 wrote: post #50

Wow his database startup that raised 12M died this year after only three years. If anything this shows how insanely difficult it must be to succeed as a database startup (when was the most recent startup success in this space?), as the founding team is stellar. On the other hand I am surprised it died this quick and interested to know if they did a proper postmortem. Not only did they raise way more than is needed to…

I thought the same thing. I have a personal project that started out as a file system replacement (object store), but also does some amazing DB operations and is useful for analytics. I have often thought about trying to turn it into a profitable business; but the thought of needing to raise insane amounts of capital just to get a few years of runway, seems daunting.

Re: Databases in 2024: A Year in Review

#118

Post by jghn »

tayo42 wrote: post #48
antirez wrote: post #14

Wow, 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

Right there with you. The trend towards video content instead of written sucks so much.

Re: Databases in 2024: A Year in Review

#119

Post by greggyb »

stackskipton wrote: post #78
codeulike wrote: post #17

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

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…

I'll probably come across as a shill here, but there is a lot going on with SQL Server, all included in your license (Standard Edition has limitations on scaling).

Some of these things are merely passable, some are great, but it's all included. The key takeaway is that SQL Server is a full data platform, not just an RDBMS.

- RDBMS: very solid, competitive in features - In-memory OLTP: (really a marketing name for a whole raft of algorithmic and architectural optimization) can support throughput that is an order of magnitude higher - OLAP: Columnstore index in RDBMS, can support pure DW style workload or OLAP on transactional data for near-real-time analytics - OLAP: SSAS: two different best-in-class OLAP engines: Multidimensional and Tabular for high-concurrency low-latency reporting/analytics query workloads - SSIS: passable only, but tightly integrated ETL tool; admittedly in maintenance mode - SSRS: dependable paginated / pixel-perfect reporting tool; similar to other offerings in this space - Native replication / HA / DR (one of the only things actually gated behind Enterprise) - Data virtualization: PolyBase

If you're just looking for a standard RDBMS, then there's little to justify the price tag for SQL Server. If you want to get value for money, you take advantage of the tight integration of many features.

There is value for having these things just work out of the box. How much value is up to you and your use cases.

Re: Databases in 2024: A Year in Review

#120

Post by lmwnshn »

dig1 wrote: post #32

> There was no major effort to fork off MongoDB, Neo4j, Kafka, or CockroachDB when they announced their license changes. AFAIK people didn't take MongoDB seriously from the start, especially with the "web scale database" joke circulating. The Neo4j Community version has been under GPLv3 for quite some time, while the Enterprise version has always been somewhat closed, regardless of whether the source code was availab…

> ... you should not recruit the university department/group/students against your peers ...

As a student who chose to stay at CMU for a PhD because of this group, it is quite the opposite situation - you may also misunderstand the nature of the "ban" (students can still apply directly to the company).

From the student perspective, we benefit from knowing the reputation of potential employers. For example: CompanyX went back on their promises so don't trust them unless they give it to you right away, CompanyY has a culture of being stingy, the people who went to CompanyZ love it there, and so on.

So it's more like (1) providing additional data about the company's past behavior, and (2) not actively giving the company a platform. I personally find this great for students.

Post reply on HN