Why Use Postgres Anymore?
When Postgres loyalty gets seriously challenged today
Jason AllumGuest
Jacob LuetzowHost
I mean, it's like the, uh, the amazingness of, like, the BEAM or Erlang too, like, the problems they solved back in the '80s are recurring problems now with AI and agents and processes, whatever you might need.

And then the BEAM is, I mean, to refresh people's memory, it's like almost 40 years old.

And so you have these things where, like, the, the underpinnings of it, some of the stuff has changed underneath, right? But the basic way that it works is fairly, fairly s- you know, locked in.

And you have these, this idea where you have small processes, you have, you know, sh- not shared memory so they can do whatever they want with their little, their little corner of the universe, and then they trade things with messages.

Like, this has become a, a, a really powerful pattern, and it works well for all kinds of the more modern problems, not just dealing with telephone switches or whatever it was that they built it for originally.

It's one of the things I like about different languages and things is you can try on a different head space, right? Like, there's a different way of thinking that goes with each one of these things.

You have the BEAM, and there's a certain way of thinking that goes along with it.

You got Go or Rust or C++, any of these other things, right? And there's a, a, a, a, just kind of a head space that goes along with it, and it's kind of fun to try them on a little bit.

... pick up things from one place and bring them to another, right? Like, I just had a, a Rust project I was working on and I brought Elixir style telemetry over to it because it made it easier to, to, to get at certain problems, you know? And it's, it's interesting that sometimes people don't play with things that are outside of their normal wheelhouse, and I think they miss out a little bit because there's interesting ways to solve problems, and if you don't look, you don't see.

I mean, immutable data, I mean, just being able to think about the, "I put that there, it's gonna stay there.

I mean, it's like the, uh, the amazingness of, like, the BEAM or Erlang too, like, the problems they solved back in the '80s are recurring problems now with AI and agents and processes, whatever you might need.

And then the BEAM is, I mean, to refresh people's memory, it's like almost 40 years old.

And so you have these things where, like, the, the underpinnings of it, some of the stuff has changed underneath, right? But the basic way that it works is fairly, fairly s- you know, locked in.

And you have these, this idea where you have small processes, you have, you know, sh- not shared memory so they can do whatever they want with their little, their little corner of the universe, and then they trade things with messages.

Like, this has become a, a, a really powerful pattern, and it works well for all kinds of the more modern problems, not just dealing with telephone switches or whatever it was that they built it for originally.

It's one of the things I like about different languages and things is you can try on a different head space, right? Like, there's a different way of thinking that goes with each one of these things.

You have the BEAM, and there's a certain way of thinking that goes along with it.

You got Go or Rust or C++, any of these other things, right? And there's a, a, a, a, just kind of a head space that goes along with it, and it's kind of fun to try them on a little bit.

... pick up things from one place and bring them to another, right? Like, I just had a, a Rust project I was working on and I brought Elixir style telemetry over to it because it made it easier to, to, to get at certain problems, you know? And it's, it's interesting that sometimes people don't play with things that are outside of their normal wheelhouse, and I think they miss out a little bit because there's interesting ways to solve problems, and if you don't look, you don't see.

I mean, immutable data, I mean, just being able to think about the, "I put that there, it's gonna stay there.
Every episode on Radar is fully transcribed, speaker-labeled, and rich with metadata. Here is a taste of this one. Try Radar for free to see the rest.
3 of 7
Why Use Postgres Anymore?
When Postgres loyalty gets seriously challenged today
Zero-Copy Binary Secret
Discover why binaries suddenly turbocharge BEAM performance
Bedrock’s Conflict Solution
How Bedrock decides winners in simultaneous writes
+4 more clips · 3 min 24 sec of audio in all
7 of 17
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
All 7 clips — the highlight moments, each cut as its own audio, with a title and a speaker
All 12 segments — the transcript broken into labeled sections, every ad read marked
All 17 topics — jump to every other episode discussing the same subject
Every related episode — other shows Radar links to this one
No account is needed to search Radar.