Repository navigation
Replies: 1 comment
|
Keeping so much useful information in relation database has performance problems. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
- 7FB2
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
One of the advantages of using Keycloak (KC) is that its database is relatively small. This keeps operations simple, you can take a backup, restore it quickly, and recover easily when something goes wrong.
Now, I’d like to focus specifically on the EVENT_ENTITY table. Instead of storing this audit-style data in the Keycloak database, wouldn’t it be better to add native support for pushing these events to external systems that are more suitable for this purpose, such as Kafka or OpenSearch, without relying on additional components like CDC and sink connectors?
The Keycloak production database is really not an ideal place to store large volumes of audit logs, IMHO.
All reactions