This is an automated email from the ASF dual-hosted git repository.

kmiller pushed a commit to branch feature/GEODE-4997
in repository

commit 9b5c43e86194f990526de0d5073477bafb31adb1
Author: Karen Miller <>
AuthorDate: Fri Apr 6 14:49:34 2018 -0700

    GEODE-4997: work in progress, document inline caching with Geode
 geode-docs/use_cases/ | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/geode-docs/use_cases/ 
index 87e1e5b..1a2bab3 100644
--- a/geode-docs/use_cases/
+++ b/geode-docs/use_cases/
@@ -22,9 +22,13 @@ An inline cache holds region entries for a client 
 ## Description of an Inline Cache
-A cache is formed from a region within a <%=vars.product_name%> cluster,
-and the cache sits between the client application and a
+An inline cache holds data for quick access.
+The inline cache comprises 
+a Geode region together with code deployed to servers that host 
+the region.
+The inline cache sits between the client application and a
 backing data store.
+The server-deployed code communicates with the backend data store.
 <img src="../images/inline-cache.png" id="inline-cache-png" class="image" />
@@ -36,9 +40,10 @@ it quickly responds with the value for a lookup operation.
 This is a cache hit.
 If the requested region entry is not in the region,
 it is a cache miss,
-and code that has been deployed to the server acquires the
+and the code deployed to the server acquires the
 entry from the data store.
-The acquired region entry is written to the region
+<GEODE> writes the
+acquired region entry to the region
 such that future lookups will cause a cache hit.
 ## Implementation and Configuration

To stop receiving notification emails like this one, please contact

Reply via email to