Isn't the database already one of the hardest piece of infras to scale? Why would you want to load it with additional long-running jobs?

Long-running jobs on Postgres are not new at all. See pg_cron for one example. At the end of the day, these workloads would be running anyway against the database, whether triggered by an external component. HTTP queries from the database have also become more popular to avoid round-trips and failure points from additional components in data or AI pipelines. But yes, whether to bring the compute to the data or vice-versa is a design choice that has a lot of contention.

Gotta set up the fall to rake in the dough later with consulting fees