Article doesn't make sense. Some of the "horizontally scaled" servers have their own state. A local cache, a temporary filesystem etc.

Also, has teh author never heard of long running queued jobs? Or long running scheduled jobs? They ultimately report back into the DB (updating their status etc).

This article reeks of someone using AI to make huge leaping jumps of logic. The "single source of truth" rule has survived this long for a reason. It works!

▲

zknill 5 hours ago | parent [-]

And once those long running jobs have reported their status back to the database, how will the client find out about that status?

Please, please, please don't say "polling". Because you've clearly missed the entire argument of the article if you say polling.

▲

dial9-1 4 hours ago | parent [-]

postgresql has LISTEN and NOTIFY. redis and kafka have pubsub. this is a solved problem

	▲	zknill 2 hours ago \| parent [-]
		Isn't the point that you no longer have a connection to the client? So you can be notified by the database, but you can't (with the stateless HTTP + loadbalancer design explained in the article) get that notification back to the client. Because the client isn't connected anymore; so how does the client know that there's new information?