Goals:

To reduce service latency by avoiding expensive HTTP fetches whenever possible.

Overview:

When an edit is made to a ZObject, that ZObject's definition will also be added to (or updated in) memcached.
The orchestrator will also read from memcached when possible.

Acceptance Criteria:

Edits to ZObjects are being made in memcached as well as the DB.
The orchestrator is able to read from memcached and still fall back to HTTPS.