Lower the amount of PostgreSQL Connections created by Fody-API

[dmth]

Currently the tickets and events api are creating alot of connections to the database. This Value could be lowered by a more intelligent design.

[bernhardreiter]

checkticket and contactdb backend are reusing one postgresql connection per process, what the difference to the ticket and events backends? Or are the connections build because a new process is created per request (which should not be the case when serving via wsgi hug and apache2 in the example config).

[dmth]

Every endpoint (/events, /tickets, /checkticket, /contactdb) creates one connection to the database.
In addition there are connections from postgresql-output, intelmq-mailgen, and contact-db expert.

This sums up to 7 simultaneous connections. I wonder why this seems to be problem.

[bernhardreiter]

Some must use a different connection because they have to use different credentials.
But seven connection should be fine, we could potentially save a few, but this looks like small value. Am I right?