Logo

dev-resources.site

for different kinds of informations.

Using Caching in React with useGetProducts: Improve Performance and UX

Published at
11/12/2024
Categories
react
frontend
cache
performance
Author
matan3sh
Categories
4 categories in total
react
open
frontend
open
cache
open
performance
open
Author
8 person written this
matan3sh
open
Using Caching in React with useGetProducts: Improve Performance and UX

In this blog post, we'll walk through how to implement a React hook that retrieves data with a cache-first approach, fetching data from a backend only when necessary. The goal is to demonstrate how caching can improve the user experience (UX) by reducing latency and making the app feel faster.

We'll be using a utility function to interact with the cache stored in IndexedDB and demonstrate the process of fetching product data from an API with high latency. This approach reduces the waiting time for users by showing cached data immediately and refreshing the data in the background.

The Problem: High Latency API Calls

Imagine you're building an app that fetches product data from an API. In real-world scenarios, this data may come from a remote server with latency (e.g., 2-3 seconds delay). While waiting for the data, users may feel frustrated. So, how do we solve this problem?

By caching the data using IndexedDB, we can immediately display previously fetched data to users, even while new data is being fetched in the background. This gives users a faster and smoother experience.

Step-by-Step Breakdown of useGetProducts

Let's break down the useGetProducts hook that handles the cache logic and API calls.

Step 1: Define the Product Interface

First, we define the Product interface to represent the data we are working with:

interface Product {
  id: number
  name: string
}
Enter fullscreen mode Exit fullscreen mode

This is a simple object structure with id and name representing a product.

Step 2: Simulate an API Call with Latency

Next, we simulate an API call using the getProducts function, which has a built-in delay of 2 seconds to mimic a real backend API with high latency:

const getProducts = async (): Promise<Product[]> => {
  return await new Promise<Product[]>((resolve) =>
    setTimeout(
      () =>
        resolve([
          { id: 1, name: 'Product A' },
          { id: 2, name: 'Product B' },
        ]),
      2000
    )
  )
}

Enter fullscreen mode Exit fullscreen mode

This function simulates a delayed API call that returns an array of products after 2 seconds.

Step 3: The useGetProducts Hook

Now, let's build the useGetProducts hook. The core idea is that we check if there's cached data available first and use it immediately, then fetch fresh data in the background.

const useGetProducts = (): {
  data: Product[] | undefined
  loading: boolean
} => {
  const [products, setProducts] = React.useState<Product[] | undefined>(
    undefined
  )
  const [loading, setLoading] = React.useState(true)
  const cacheKey = 'cache_products'

  // Load products from cache, then fetch from API to update if cache is used.
  const loadProducts = React.useCallback(async () => {
    setLoading(true)

    // Step 1: Load from cache, if available, for immediate display
    const cachedProducts = await getCachedData<Product[]>(cacheKey)
    if (cachedProducts && cachedProducts.length > 0) {
      setProducts(cachedProducts) // Display cached data immediately
      setLoading(false)
    }

    // Step 2: Fetch updated data from API, even if cache was used
    try {
      const response = await getProducts()
      setProducts(response) // Update with fresh data
      updateCache(response, cacheKey) // Update the cache with new data
    } catch (err) {
      console.error('Error fetching products:', err)
    } finally {
      setLoading(false)
    }
  }, [])

  React.useEffect(() => {
    loadProducts()
  }, [loadProducts])

  return { data: products, loading }
}

Enter fullscreen mode Exit fullscreen mode

Explanation:

  1. State Management: We use React.useState to manage two pieces of state:
  2. products: The array of product data.
  3. loading: A flag to indicate whether the data is still being fetched.

  4. Cache Lookup: In the loadProducts function, we first try to fetch the product data from the cache using the getCachedData function. If cache data exists, it will be shown immediately, and loading will be set to false.

  5. API Call: Simultaneously, we make an API call to fetch fresh data using the getProducts function. Once the new data is fetched, we update the state and cache it for future use using the updateCache function.

  6. Optimistic UI: This approach helps improve the UX because it shows cached data right away, while fresh data is loaded in the background, reducing perceived latency.

Step 4: Caching Utility Functions

The caching is powered by two utility functions, getCachedData and updateCache, which interact with IndexedDB to store and retrieve data.

  • getCachedData: This function retrieves the cached data from IndexedDB.

  • updateCache: This function stores the fresh data in IndexedDB to be used for future requests.

By using IndexedDB, we ensure that data persists even if the user reloads the page or navigates away.

import {
  deleteFromIndexedDB,
  getAllKeysFromIndexedDB,
  getFromIndexedDB,
  saveToIndexedDB,
} from '../indexDb'

const encryptData = (data: string): string => btoa(encodeURIComponent(data))
const decryptData = (encryptedData: string): string =>
  decodeURIComponent(atob(encryptedData))

export const updateCache = async <T>(data: T, cacheKey: string) => {
  try {
    const [, cacheConst] = cacheKey.split('_')

    const allKeys = await getAllKeysFromIndexedDB()

    const existingKey = allKeys.find((key) => key.endsWith(`_${cacheConst}`))
    if (existingKey) {
      await deleteFromIndexedDB(existingKey)
    }

    const serializedData = JSON.stringify(data)
    const encryptedData = encryptData(serializedData)
    await saveToIndexedDB(cacheKey, encryptedData)
  } catch (error) {
    console.error('Failed to update cache:', error)
  }
}

export const getCachedData = async <T>(cacheKey: string): Promise<T | null> => {
  try {
    const cached = await getFromIndexedDB(cacheKey)
    if (cached) {
      const decryptedData = decryptData(cached)
      return JSON.parse(decryptedData) as T
    }
    return null
  } catch (error) {
    console.error('Failed to retrieve cached data:', error)
    return null
  }
}

Enter fullscreen mode Exit fullscreen mode

These functions allow us to easily access and update the cache using IndexedDB in the browser, providing persistent data storage.

Step 5: Final Usage

Here's how you would use the useGetProducts hook in a component to display the products:

import React from 'react'
import useGetProducts from './useGetProducts'

const ProductList: React.FC = () => {
  const { data: products, loading } = useGetProducts()

  if (loading && !products) return <div>Loading products...</div>
  if (!products || products.length === 0) return <div>No products found.</div>

  return (
    <div>
      <h3>Available Products:</h3>
      <ul>
        {products.map(product => (
          <li key={product.id}>{product.name}</li>
        ))}
      </ul>
    </div>
  )
}

export default ProductList

Enter fullscreen mode Exit fullscreen mode

By implementing caching with IndexedDB in this way, we can significantly improve the UX of applications that rely on external APIs with high latency. The user will see cached data immediately, and the fresh data will update behind the scenes, ensuring that users always get the most up-to-date information without the wait.

This approach reduces the perceived latency of your application, making it feel faster and more responsive, even in situations where the backend might be slow.

cache Article's
30 articles in total
Favicon
Caching in Node.js: Using Redis for Performance Boost
Favicon
Building the Perfect Caching System: A Comprehensive Guide
Favicon
Cache your function computation in React Server Components
Favicon
From Heartbeats to Cache Misses: Making Big Numbers Hit Home
Favicon
Redis Cache - A String story
Favicon
Boosting Backend Performance with Distributed Cache: A Comprehensive Guide
Favicon
🌟 Mastering Caching in JavaScript for Optimizing Performance πŸš€
Favicon
Cache NLogN🏎️
Favicon
System Design 02 - Caching: The Art of Keeping Users Happy Without Breaking a Sweat
Favicon
Stale cache, the holy grail of performance
Favicon
Top 5 Caching Patterns for High-Performance Applications
Favicon
How to Effectively Handle Caching in Your Application: Lazy Loading vs Write-Through
Favicon
Using Caching in React with useGetProducts: Improve Performance and UX
Favicon
The Role of Cache Memory in Enhancing Processing Speed
Favicon
Mastering Android App Visuals: A Comprehensive Guide to Effortless Image Uploading, Storage, and Sharing.
Favicon
That way to build High-Performance APIs in .NET - Part 2: Caching
Favicon
Understanding CDN Cache in NextJs
Favicon
Supercharge your applications queries with caching
Favicon
Can Postgres replace Redis as a cache?
Favicon
Difference between cache vs cookie
Favicon
Monitor Squid Proxy with Goaccess
Favicon
Speeding Up Your Website Using Cloudflare Cache
Favicon
Finally found a solution to clear the CDN cache using GitHub Actions!
Favicon
Stale-while-revalidate and it's usage with Next.js
Favicon
Why do we need NoSql Database
Favicon
Go Redis Crud quickly example
Favicon
How to build a caching layer for your Laravel API
Favicon
Davide's Code and Architecture Notes - Cache Expiration vs Cache Eviction (and Eviction Policies)
Favicon
Entendendo porque o Cache Lock Γ© sinΓ΄nimo de integridade
Favicon
Mastering Frontend Performance: Harnessing the Power of Caching

Featured ones: