Sounds like Postgres connection scaling issues to me.
Just a wild guess but the fact that connections are heavy in pg is a foot gun that tends to rear its head during large scale-up events
Just a wild guess but the fact that connections are heavy in pg is a foot gun that tends to rear its head during large scale-up events
From the moment one runs a system in two nodes, one being the application server and the other the database server, that system is distributed. Two nodes is all it takes.
Perhaps I wasn’t clear enough, but in your comment you make it sound that having multiple nodes interacting with a database is an anti-pattern, which is not, the discipline of distributed system is well researched and from the top of my head I risk to tell you that such anti-pattern is never mentioned, and the concept of a database rarely appears in DS, instead it focuses in a more abstract concept, which are the network nodes.
To support my argument, from the moment one decides to replicate nodes, most likely those same nodes will be connected to the same data source, because data replication isn’t as trivial as application replication.
In a Microservice architecture it can be considered an anti-pattern to have different bounded contexts using the same database.