You're going to have to bear with me on this one because my thoughts aren't fully formed.

As I'm sure I've mentioned, I'm a little elderly (and you thought I was going to talk about radios). As such, I've seen the death of a few technologies. I may not have shared this widely, but my uncle ran a newspaper for a time in a small town in Missouri. They were still using hot type (literally a bath of lead turned into letters). I got to help type-set a newspaper using this when I was a kid. My uncle then went into the printing business, cold type. My introduction to computers was partly doing publishing & printing, but no hot or cold type, just PageMaker through desktop publishing. I talked to the people doing hot type who moaned about cold type and how it wasn't as good. Then I heard the cold type people moaning about desktop publishing and how it wasn't as good. I watched these technologies shrink and the jobs, mostly, die. Heck, who does desktop publishing now?

These were, to me, technological dinosaurs. Their time had come and gone. So, I've spent a career, trying hard to watch to see if I'm becoming a dinosaur. I've had a career in databases, most of it focused purely on relational data engines, and most of that SQL Server. However, lately, I've been working in PostgreSQL as well. Not because SQL Server is dying, far from it. Just because, it was pretty clear, a lot of work was happening in that space, and, I have a fear of becoming a technological dinosaur.

Now in the last few years, we've seen machine learning become, well, boring. It's pretty thoroughly embedded and becoming more so. In addition, we've seen the large language models coming along (LLMs, aka AI). There's been quite a bit of FUD (fear, uncertainty & doubt) about AI, but it's looking more and more like it's just going to be one more tool in the toolbox (although, I still have my doubts about how AI affects peoples learning & career paths, different discussion).

No, what's really changing the landscape, and has me concerned is something else entirely. Fabric. And DataBricks. And SnowFlake. Redshift. Data Lakes. All that stuff. And no, not because I see that replacing relational data stores. Nope. Not at all. Instead, what we're seeing is that no one seems to care about the relational data stores. Oh, yeah, we're still building them. OLTP (OnLine Transaction Processing for you kids out there) is mighty and strong and ongoing. Yet... No one cares about it. There even seems to be a very large indifference to it.

Why? What happened? Was there a major technology shift that we just didn't see?

Funny enough, no. Technology is pretty much transparent. OLTP is still one of the major collectors of data. That then feeds into all these magic analytical engines and the AI. So why doesn't anyone care about OLTP any more? Well, while I, and I suspect a lot of you, have been focused on watching technology to understand if I'm working on hot type, cold type, what have you, in order to protect my career, a social shift has been occurring.

See, more and more, people are just assuming that OLTP will just work. We've got Object Relational Mapping (ORM) tools to handle the code. Structures just work. If you're on the cloud, backups are handled. High availability is handled. Everything is just kind of taken care of. So, yeah, we're still using OLTP, relational databases, all the stuff I've spent 30 years learning about and supporting. It's all there. But, socially, we've stopped worrying about it. In theory (and I think this is where things get weird), it's a solved problem. All you have to do is go to a higher service tier  and all your problems are solved. Our challenges in this brave new world are all in the analytical space. Collecting data is easy. Using data is hard. This is why you see more, and more, and yet still more, Fabric/DataBricks/SnowFlake/RedShift being talked about and less and less traditional data management, monitoring, query tuning, and all the rest.

So, we've hit the technological dinosaur stage then?

No.

This is my problem. People are paying more than they should in order to make their poorly built, badly coded, horribly maintained, relational databases work. It looks like something that's not a problem, yet, it's still there. What's happened is we've socially moved on. Our attitudes have changed. The tech is in place, in operation, stinking on toast, but no one seems to worry about it any more.

And now, I'm back to wondering, am I a dinosaur, or am I the little boy pointing out that the emperor seems to be showing quite a few of his naughty bits?

Sorry for the rambling nature of this one. As I say, I'm still cogitating on this one. What do you think?