description |
---|
This article introduces how to configure various repositories |
Gravitee uses repositories to store different types of data. They are configured in gravitee.yml
, where each repository can correspond to a particular scope. For example, management data can be stored in MongoDB, rate limiting data in Redis, and analytics data in ElasticSearch.
The following matrix shows scope and storage compatibility.
Scope | MongoDB | Redis | ElasticSearch | JDBC |
---|---|---|---|---|
Management All the APIM management data such as API definitions, users, applications, and plans | true | false | false | true |
Rate Limit Rate limiting data | true | true | false | true |
Analytics Analytics data | false | false | true | false |
Distributed Sync Responsible for storing the sync state for a cluster | false | true | false | false |
Please choose from the options below to learn how to configure these repositories.
{% hint style="warning" %} Using JDBC as a rate limit repository is not recommended because concurrent threads do not share a counter. This can result in inaccuracies in limit calculations. {% endhint %}
Elasticsearch | elasticsearch.md | ||
MongoDB | mongodb.md | ||
JDBC | jdbc.md | ||
Redis | redis.md |