Cache

The cache in the United Manufacturing Hub is Redis , a key-value store that is used as a cache for the other microservices.

How it works

Recently used data is stored in the cache to reduce the load on the database. All the microservices that need to access the database will first check if the data is available in the cache. If it is, it will be used, otherwise the microservice will query the database and store the result in the cache.

Kubernetes resources

• StatefulSet: united-manufacturing-hub-redis-node
• Service:
  • Internal ClusterIP:
    • Redis: united-manufacturing-hub-redis at port 6379
    • Headless: united-manufacturing-hub-redis-headless at port 6379
    • Metrics: united-manufacturing-hub-redis-metrics at port 6379
• ConfigMap:
  • Configuration: united-manufacturing-hub-redis-configuration
  • Health: united-manufacturing-hub-redis-health
  • Scripts: united-manufacturing-hub-redis-scripts
• Secret: redis-secret
• PersistentVolumeClaim: redis-data-united-manufacturing-hub-redis-node-0

Configuration

You shouldn’t need to configure the cache manually, as it’s configured automatically when the cluster is deployed. However, if you need to change the configuration, you can do it by editing the redis section of the Helm chart values file.

Environment variables