1Z0-997-25 Question 98
Select 2You have a microservices-based eCommerce application hosted on Oracle Container Engine for Kubernetes (OKE). During seasonal sales, your application experiences traffic spikes when users rapidly browse product listings and frequently add items to their carts. You decide to leverage OCI Cache to reduce database load and improve response times. Which two strategies would best ensure optimal performance and scalability with minimal code changes?
- A
Store complete product data tables permanently in the cache, bypassing the database entirely.
- B
Implement a cache-aside pattern where your application checks the cache first and only queries the database on a cache miss.
- C
Use an on-instance disk-based cache to avoid using memory-based caching at runtime.
- D
Configure session data storage in OCI Cache to ensure that user cart information is immediately accessible by all microservices without constantly hitting the database.
- E
Enable automatic cache invalidation on a fixed interval, regardless of inventory updates, to simplify management.
Show answer and explanation
Correct answers: B, D
Explanation
For high-traffic web applications running on OKE, leveraging OCI Cache improves performance by reducing round trips to the database. A cache-aside pattern is widely recognized as a best practice: it keeps the database as the authoritative source but uses the cache for fast lookups on subsequent requests. Storing session data in OCI Cache further offloads read and write operations from the database, crucial during heavy traffic spikes such as seasonal sales. For more details, consult Oracle's documentation on 'High-Performance Caching Patterns' in OCI.
- A. Incorrect.
Option 1: Store complete product data tables permanently in the cache, bypassing the database entirely. (Incorrect) Storing entire tables in memory for an extended period or bypassing the database entirely is risky. It can lead to stale data and is not optimal for large datasets. Oracle recommends strategies like cache-aside or write-through patterns, rather than trying to hold all data in the cache indefinitely.
- B. Correct.
Option 2: Implement a cache-aside pattern where your application checks the cache first and only queries the database on a cache miss. (Correct) This is a recognized best practice. With cache-aside, you fetch from the cache first to reduce database hits, and you only query the database when data is not already in the cache. Once you get a cache miss, you load the data from the database into the cache for subsequent fast reads.
- C. Incorrect.
Option 3: Use an on-instance disk-based cache to avoid using memory-based caching at runtime. (Incorrect) Disk-based caching typically introduces higher latency compared to in-memory solutions. OCI Cache is designed for in-memory, highly performant caching, which is much faster for frequent read operations.
- D. Correct.
Option 4: Configure session data storage in OCI Cache to ensure that user cart information is immediately accessible by all microservices without constantly hitting the database. (Correct) By storing session data (like cart info) in OCI Cache, you can minimize repeated database calls. This also helps ensure all microservices have real-time access to the same session data, boosting performance and consistency.
- E. Incorrect.
Option 5: Enable automatic cache invalidation on a fixed interval, regardless of inventory updates, to simplify management. (Incorrect) Invalidating the cache solely by time interval risks stale or incorrectly invalidated data. Proper cache invalidation should consider real-time updates such as inventory changes, not just a rigid schedule.