I completely agree with your view! I use postgres for all, as the cost of switching to the (scalable) solution for this kind of problems is low, and in the ens let’s be realistic about how “viral” your app can get…

When I worked in a bigger company in the past we used postgres to store raw blobs for data transformation pipelines (+1T table), and queries to it were instant due to good index usage. Others might have gone to BigQuery or something else making more complex and def more expensive.

PS: I love tools like Temporal, Hatchet or Oban that rely on Postgres and can scale a ton too.