{"id":5831,"date":"2026-06-16T06:30:01","date_gmt":"2026-06-16T06:30:01","guid":{"rendered":"https:\/\/aaxonix.com\/resources\/?post_type=glossary&#038;p=5831"},"modified":"2026-06-16T06:30:01","modified_gmt":"2026-06-16T06:30:01","slug":"cache-zoho-catalyst","status":"publish","type":"glossary","link":"https:\/\/aaxonix.com\/resources\/glossary\/cache-zoho-catalyst\/","title":{"rendered":"Cache"},"content":{"rendered":"<style>\n.gt-body{font-family:'Poppins',sans-serif;color:#111;line-height:1.7;max-width:860px;margin:0 auto;padding:0 0 48px}\n.gt-type-badge{display:inline-block;font-size:11px;font-weight:600;letter-spacing:1.5px;text-transform:uppercase;color:#E8650A;border:1px solid rgba(232,101,10,.25);border-radius:20px;padding:3px 12px;margin-bottom:16px}\n.gt-def{font-size:17px;line-height:1.75;color:#1a1a1a;padding:20px 24px;background:#F7F4EF;border-left:3px solid #E8650A;border-radius:0 8px 8px 0;margin-bottom:28px}\n.gt-section{margin-bottom:28px}.gt-section h2{font-size:18px;font-weight:700;color:#0A1628;margin-bottom:12px;padding-bottom:8px;border-bottom:1px solid #DDD8CF}\n.gt-section p{font-size:15px;color:#333;margin-bottom:10px}\n.gt-example-box{background:#0A1628;color:#fff;border-radius:10px;padding:24px 28px;margin:28px 0}\n.gt-example-box h3{font-size:14px;font-weight:600;color:#E8650A;text-transform:uppercase;letter-spacing:1px;margin-bottom:10px}\n.gt-example-box p{font-size:14px;line-height:1.7;color:rgba(255,255,255,.85);margin:0}\n.gt-related-pills{display:flex;flex-wrap:wrap;gap:8px;margin:28px 0}\n.sp-content-link{display:inline-block;font-size:13px;font-weight:500;color:#2563EB;border:1px solid rgba(37,99,235,.25);border-radius:20px;padding:5px 14px;text-decoration:none}\n.gt-faq-item{border:1px solid #DDD8CF;border-radius:10px;padding:18px 20px;margin-bottom:12px}\n.gt-faq-item h3{font-size:15px;font-weight:600;color:#0A1628;margin-bottom:8px}\n.gt-faq-item p{font-size:14px;color:#555;margin:0;line-height:1.65}\n<\/style>\n<div class=\"gt-body\">\n  <span class=\"gt-type-badge\">Feature<\/span><\/p>\n<div class=\"gt-def\">Catalyst Cache is a managed in-memory key-value store that stores frequently accessed data with a configurable time-to-live, so serverless functions can retrieve it in milliseconds instead of querying the Datastore or calling an external API on every invocation.<\/div>\n<div class=\"gt-section\">\n<h2>How Cache Works in Zoho Catalyst<\/h2>\n<p>The Catalyst SDK provides put, get, and delete methods for the Cache service. You write a value to a named key with an optional TTL in seconds; after the TTL expires, the entry is automatically removed. Cache is shared across all running instances of your Catalyst project, so one function instance can write data that another instance reads in a subsequent request. Values can be strings or serialised JSON objects.<\/p>\n<\/p><\/div>\n<div class=\"gt-section\">\n<h2>When to Use Cache<\/h2>\n<p>Use Cache when a function repeatedly needs data that changes infrequently, such as a list of active product SKUs, a GST rate table, or a set of configuration values fetched from the Datastore. Caching these for five to ten minutes dramatically reduces Datastore read operations and speeds up function response times. Indian SaaS teams with high request volumes use Catalyst Cache to keep function latency low during peak business hours without scaling up their Datastore plan.<\/p>\n<\/p><\/div>\n<div class=\"gt-section\">\n<h2>Key Considerations<\/h2>\n<p>Cache is volatile; all entries are lost if the Catalyst cache service restarts, so never use it as a primary data store. Always code defensively by checking whether a cache miss occurred and falling back to the Datastore. Choose TTL values carefully: too short and you lose the performance benefit; too long and functions may serve stale data after an update.<\/p>\n<\/p><\/div>\n<div class=\"gt-example-box\">\n<h3>India Example<\/h3>\n<p>A Chennai-based B2B marketplace uses a Catalyst function to serve product pricing in response to buyer API calls. The pricing table in the Datastore has 5,000 rows updated once a day. The function caches the entire pricing map in Catalyst Cache with a 12-hour TTL. During peak hours, 95 percent of pricing requests are served from cache, reducing Datastore queries from 50,000 to under 3,000 per day and cutting function execution time by 80 milliseconds per call.<\/p>\n<\/p><\/div>\n<div class=\"gt-related-pills\">\n    <a href=\"\/resources\/glossary\/datastore-zoho-catalyst\/\" class=\"sp-content-link\">Datastore<\/a><br \/>\n    <a href=\"\/resources\/glossary\/serverless-function-zoho-catalyst\/\" class=\"sp-content-link\">Serverless Function<\/a><br \/>\n    <a href=\"\/resources\/glossary\/nosql-table-zoho-catalyst\/\" class=\"sp-content-link\">NoSQL Table<\/a><br \/>\n    <a href=\"\/resources\/glossary\/catalyst-sdk-zoho-catalyst\/\" class=\"sp-content-link\">Catalyst SDK<\/a>\n  <\/div>\n<div class=\"gt-faq-item\">\n<h3>What data types can be stored in Catalyst Cache?<\/h3>\n<p>Catalyst Cache stores string values. To cache complex objects such as arrays or JSON maps, serialise them to a JSON string before writing to the cache and parse them back after reading. The Catalyst SDK&#8217;s cache methods accept and return strings, so this serialisation step is the developer&#8217;s responsibility.<\/p>\n<\/p><\/div>\n<div class=\"gt-faq-item\">\n<h3>Is Catalyst Cache shared between development and production environments?<\/h3>\n<p>No. Catalyst Cache is scoped to the environment (development or production) within a project. A cache entry written in the development environment is not visible in production, which prevents test data from interfering with live application behaviour.<\/p>\n<\/p><\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Cache in Zoho Catalyst is an in-memory key-value store that lets serverless functions read and write temporary data at high speed to avoid repeated database queries or API calls.<\/p>\n","protected":false},"template":"","meta":{"seo_title":"Cache | Zoho Catalyst Glossary","seo_description":"Cache in Zoho Catalyst is an in-memory key-value store that lets serverless functions read and write temporary data at high speed to avoid repeated database queries.","seo_keyword":"cache zoho catalyst","seo_faqs":"[{\"q\": \"What data types can be stored in Catalyst Cache?\", \"a\": \"Catalyst Cache stores string values. To cache complex objects such as arrays or JSON maps, serialise them to a JSON string before writing to the cache and parse them back after reading. The Catalyst SDK's cache methods accept and return strings, so this serialisation step is the developer's responsibility.\"}, {\"q\": \"Is Catalyst Cache shared between development and production environments?\", \"a\": \"No. Catalyst Cache is scoped to the environment (development or production) within a project. A cache entry written in the development environment is not visible in production, which prevents test data from interfering with live application behaviour.\"}]","term_type":"Feature","glossary_related":"","glossary_links":""},"glossary_category":[1294],"class_list":["post-5831","glossary","type-glossary","status-publish","hentry","glossary_category-zoho-catalyst"],"_links":{"self":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/glossary\/5831","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/glossary"}],"about":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/types\/glossary"}],"wp:attachment":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/media?parent=5831"}],"wp:term":[{"taxonomy":"glossary_category","embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/glossary_category?post=5831"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}