Databases store stuff really well. If get to the level of needing to configure storage for different tiers of access they can do that, it just takes a bit of work. Of course if your blob data is stored in tables that have OLTP data in them, then you have a bit of work to do to separate it out.

This is speaking from recent experience of having to manage random blobs of sensitive data in s3 buckets that engineers have created rather than bothering to put in the main application data store.

Storing attachments as a blob in a database has all sorts of disadvantages I'm sure you're aware of, but it has the major advantage that if you can see the reference to the attachment, you can fetch the attachment. With links to a filesystem, you have to deal with issues like the frontends can't access the files because they're on the wrong system, or the network filesystem is down or .... There's a lot of possibilities.