zitadel/cmd/mirror
Silvan 4645045987
refactor: consolidate database pools (#9105)
# Which Problems Are Solved

Zitadel currently uses 3 database pool, 1 for queries, 1 for pushing
events and 1 for scheduled projection updates. This defeats the purpose
of a connection pool which already handles multiple connections.

During load tests we found that the current structure of connection
pools consumes a lot of database resources. The resource usage dropped
after we reduced the amount of database pools to 1 because existing
connections can be used more efficiently.

# How the Problems Are Solved

Removed logic to handle multiple connection pools and use a single one.

# Additional Changes

none

# Additional Context

part of https://github.com/zitadel/zitadel/issues/8352
2025-01-16 11:07:18 +00:00
..
auth.go refactor: consolidate database pools (#9105) 2025-01-16 11:07:18 +00:00
config.go feat(v3alpha): web key resource (#8262) 2024-08-14 14:18:14 +00:00
defaults.yaml feat(cmd): mirror (#7004) 2024-05-30 09:35:30 +00:00
event_store.go refactor: consolidate database pools (#9105) 2025-01-16 11:07:18 +00:00
event.go fix(eventstore): revert precise decimal (#8527) (#8679) 2024-09-24 18:43:29 +02:00
mirror.go fix(mirror): read config correctly (#8330) 2024-07-18 14:00:58 +00:00
projections.go refactor: consolidate database pools (#9105) 2025-01-16 11:07:18 +00:00
system.go refactor: consolidate database pools (#9105) 2025-01-16 11:07:18 +00:00
verify.go refactor: consolidate database pools (#9105) 2025-01-16 11:07:18 +00:00