zitadel/internal/notification
Silvan 77cd430b3a
refactor(handler): cache active instances (#9008)
# Which Problems Are Solved

Scheduled handlers use `eventstore.InstanceIDs` to get the all active
instances within a given timeframe. This function scrapes through all
events written within that time frame which can cause heavy load on the
database.

# How the Problems Are Solved

A new query cache `activeInstances` is introduced which caches the ids
of all instances queried by id or host within the configured timeframe.

# Additional Changes

- Changed `default.yaml`
  - Removed `HandleActiveInstances` from custom handler configs
- Added `MaxActiveInstances` to define the maximal amount of cached
instance ids
- fixed start-from-init and start-from-setup to start auth and admin
projections twice
- fixed org cache invalidation to use correct index

# Additional Context

- part of #8999
2024-12-06 11:32:53 +00:00
..
channels feat(notification): use event worker pool (#8962) 2024-11-27 15:01:17 +00:00
handlers refactor(handler): cache active instances (#9008) 2024-12-06 11:32:53 +00:00
messages feat(OIDC): add back channel logout (#8837) 2024-10-31 15:57:17 +01:00
senders feat(OIDC): add back channel logout (#8837) 2024-10-31 15:57:17 +01:00
static feat(i18n): add korean language support (#8879) 2024-12-02 13:11:31 +00:00
statik chore: initial version of a devcontainer (#6352) 2023-08-15 10:49:05 +02:00
templates feat: add http as sms provider (#8540) 2024-09-06 13:11:36 +00:00
types fix(notifications): bring back legacy notification handling (#9015) 2024-12-06 10:56:19 +01:00
channels.go feat(OIDC): add back channel logout (#8837) 2024-10-31 15:57:17 +01:00
projections.go fix(notifications): bring back legacy notification handling (#9015) 2024-12-06 10:56:19 +01:00