This is a NON-BREAKING change. The old API still works, but the new one is executed first. If the API-KEY hasn't been defined in the new format ( as JSON ), it would read the old format ( individual Redis fields ).

In the old format all the fields associated with an API-KEY were stored using HMSET i.e.

HMSET cachedkey:$key:$service_id service-id $service_id

In the new format we're using the same Redis Key but we're storing the metadata into a new field called metadata, using HSET. This field stores a JSON string.

Since both HSET and HMSET are working on the same Redis Key the new implementation is additive and non breaking, as it simply adds a new field to the existing hash. If HGET cachedkey:$key:$service_id metadata returns the JSON, its value is used, else the API-KEY validator will try to do an HMGET on the other fields.