mirror of
https://github.com/andwati/zitadel.git
synced 2026-11-02 12:22:15 +00:00
docs: Mark beta features (#9337)
# Which Problems Are Solved Currently it is not always obvious if a feature is in beta state, also I don't know where I can add my feedback if I test the feature. # How the Problems Are Solved - Mark beta features with [beta] in sidenav - Add note on feature description where to add feedback
This commit is contained in:
@@ -1,12 +1,14 @@
|
||||
---
|
||||
title: Caches
|
||||
sidebar_label: Caches
|
||||
sidebar_label: Caches [Beta]
|
||||
---
|
||||
|
||||
ZITADEL supports the use of a caches to speed up the lookup of frequently needed objects. As opposed to HTTP caches which might reside between ZITADEL and end-user applications, the cache build into ZITADEL uses active invalidation when an object gets updated. Another difference is that HTTP caches only cache the result of a complete request and the built-in cache stores objects needed for the internal business logic. For example, each request made to ZITADEL needs to retrieve and set [instance](/docs/concepts/structure/instance) information in middleware.
|
||||
|
||||
:::info
|
||||
Caches is currently an [experimental beta](/docs/support/software-release-cycles-support#beta) feature.
|
||||
|
||||
Test the feature and add improvement or bug reports directly to the [github repository](https://github.com/zitadel/zitadel) or let us know your general feedback in the [discord thread](https://discord.com/channels/927474939156643850/1332343909900222506)!
|
||||
:::
|
||||
|
||||
## Configuration
|
||||
|
||||
Reference in New Issue
Block a user