Skip to main content
Feedback

Cloud API Management (Control Center) and Database Interaction (added in v6.2.0)

Table Design

  1. Endpoints and services are stored as CLOBs. The loader parses and converts these CLOBS to Java objects and stores them in cache. The traffic manager does not read the CLOBS from the database.

  2. The cache stores the Daily and Monthly counters in the database. These values are only used when all Cache pods are being drained. They are not loaded when some cache pods are present to avoid affecting the current counts.

  3. Tokens are stored as normalized tables, which Traffic Manager uses to create and refresh tokens and look up tokens not already cached. The loader does not load tokens.

Database Interaction

  1. The Loader handles the bulk of database operations. Most writes happen during the initial load in tethered mode. After that, the number of writes depends on changes made in the Cloud API Management Control Center. The Loader then runs on 15-minute schedules (which you can customize) to write delta updates to the database and load them into the cache.

  2. The Traffic manager’s interaction with the database is limited to reading and writing tokens and case of package keys; it can fall back on the database to read package keys if the key is not present in the cache.

  3. ConfigUI and Platform API are very limited in tethered mode, but in untethered mode, it is quite active as a database consumer.

  4. Cache only uses the database to store updated daily and monthly API call counters. It will still function without the database.

On this Page