When everything obvious fails... there are still optimisation tricks available for your databases.

I definitely would like to have some time to fiddle with DuckDB more. It looks like a really neat alternative to something like pandas.

Things went too far with the cloud monoculture. It's time to remember that it doesn't always makes sense, and in the case of databases maybe it's rarely worth it to go for fully managed options.

Looks like a nice kit to add to your tool belt. Does some handy checks if you have a Postgres database to manage.

Long but nice post about all the things you need to figure out about working with databases when the only thing you know is imperative languages.

Indeed, in most case you don't need the extra complexity. Also interesting is showing that even if the application has to scale rapidly you still got quite some time to plan the transition to something else. It makes Postgres a sane default choice.

Looks like an interesting alternative to pulling a full blown ETL for pushing data to ElasticSearch.

This article is short but very interesting. That's indeed something to keep in mind when using Postgres, you could have surprisingly bad performance results in some cases otherwise.

Yes an external cache is definitely faster. That said does your application need the extra complexity? Is the caching in database really the bottleneck? If not, the question of the external cache is still open.

Indeed they did plan ahead very well. It's no surprise if Postgres is doing so well this days.

Maybe time to change habits on table naming? I'm still on the fence myself but there are interesting arguments there.

Databases do improve and provide more "cache like" features, but such caches are still needed for the time being.

This is indeed an area which could be better handled in SQLite. It needs to be carefully checked when introduced in a project.

Indeed, if you can guarantee your materialized views to always be up to date, you might be able to get rid of some caching... and thus some complexity can be avoided.

Interesting, it looks like index scans in your databases can have surprising performance results with SSDs.

An oldie but a goodie about SQL injection. Does a good job getting the overall picture of this particular security plague.

Wow, this was a really bad index corruption indeed.

This is indeed a metaphor which should be more common in enterprise software.

Looks like a good resource to better understand indices in relational databases.

Indeed, more metadata in your database can be a life saver.