Edit 'Caching with Apache Geode' chapter by moving references to the Guide and Sample code for 'Inline Caching' under the 'Synchronous Inline Caching' sub-section.
This commit is contained in:
@@ -236,9 +236,6 @@ that might have been changed by other clients accessing the same data.
|
||||
[[geode-caching-provider-inline-caching]]
|
||||
==== Inline Caching
|
||||
|
||||
TIP: Refer to the corresponding Sample link:guides/caching-inline.html[Guide] and {github-samples-url}/caching/inline[Code]
|
||||
to see _Inline Caching_ using {geode-name} in action!
|
||||
|
||||
The next pattern of caching we will discuss in this chapter is _Inline Caching_.
|
||||
|
||||
There are two different configurations of _Inline Caching_ that developers can apply to their Spring Boot applications
|
||||
@@ -251,6 +248,9 @@ external data source.
|
||||
[[geode-caching-provider-inline-caching-synchronous]]
|
||||
===== Synchronous Inline Caching
|
||||
|
||||
TIP: Refer to the corresponding Sample link:guides/caching-inline.html[Guide] and {github-samples-url}/caching/inline[Code]
|
||||
to see _Inline Caching_ using {geode-name} in action!
|
||||
|
||||
When employing _Inline Caching_ and a cache miss occurs, the application service method may still not be invoked since
|
||||
a cache can be configured to invoke a loader to load the missing entry from an backend, external data source.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user