Good way to understand two phase locking better, its tradeoffs, variants and how it's been improved.
Good primer about database transactions and the issues you might run with when using them.
This is more manual work of course but too often forgotten. This way you get easier database migrations in complex environments though.
Everything you wanted to know about SQL joins, and more.
Excellent points. Don't be fooled by alluring architecture changes. Always keep the complexity in check and favor tuning what's already here or changing your use patterns to meet the performance you need.
Looks like an interesting extension for Postgres to do vector similarity searches inside the database.
Interesting proof of concept. I wonder how far this will go. There is definitely a need in any case.
I don't understand the SQL shaming I see in some circles. It's clearly based on dubious arguments.
Updating database schema or interfaces between services should take time if you want to limit the downtime. The extra work involved might mean you should accept a little downtime instead. It probably should be on a case by case basis rather than a blanket policy.
Nice set of tips, I knew a few but not all of them. The discussion around CTEs is interesting.
They were probably using RabbitMQ for the wrong scenario in the first place. That said it's a good reminder that sometimes a simpler architecture is what you want and it can bring benefits.
Good overview on database sharding. Points to a couple of tools which can help in some situations.
A sound list of advises, applicable to most database systems of course.
Yet another article about Postgres full test search features. This one has the advantage of giving us a glimpse about the other available options. Sometimes you want something typo resistant for instance.
Looks like an interesting tool when you need to diff databases. Definitely something I'd see myself using for large pin tests.
Nice primer on how Redis works and the type of deployments you can choose from.
This is not done often, but when you need it... you need it.
Nice little database pattern to avoid row contention with counters.
This shows quite well why I stay away from Spring Data JPA...
Interesting points about soft deletion... its usual pattern might not be what you need in the end. The proposed alternative is interesting to keep in mind.