Next.js > Optimizing calls to DatoCMS

Although the Next.js fetch API has (almost) the same interface as the regular fetch available on the browser, it is important to highlight some key differences, which might cause some surprise.

Next.js automatically does static fetches

By default, Next.js automatically does static fetches:

• For fetch calls happening in Server Components, this means that the data will be fetched at build time, cached, and reused indefinitely on each request until your next deploy.

• For fetch calls happening in Client Components, the cache lasts the duration of a session (which could include multiple client-side re-renders) before a full page reload.

Caching requests is generally a good idea, as it minimizes the number of requests made to DatoCMS. However, if you want to always fetch the latest data, you can mark requests as dynamic and fetch data on each request without caching.

GraphQL calls need to be manually deduped

It's quite common that multiple elements in the hierarchy of "things" that gets evaluated by Next.js to build a server response — layouts, pages, server components and generateMetadata/generateStaticParams functions — need to perform the same query.

Next.js automatically handles request deduping on GET requests — making sure that only one request is sent to the server — but since GraphQL requests use a POST HTTP action, we need to manually handle the case ourselves.

For this purpose, we can use a useful helper that React offers called cache, which memoizes the result of the passed function.

Our improved performRequest

Based on what we have just learned, we can refine our performRequest function, and make it more flexible and optimized:

1
import { executeQuery } from '@datocms/cda-client';
2
import { cache } from 'react';
3

4
const dedupedPerformRequest = cache(async (serializedArgs) => {
5
  return executeQuery(...JSON.parse(serializedArgs));
6
})
7

8
export function performRequest(query, options) {
9
  return dedupedPerformRequest(JSON.stringify([
10
    query,
11
    {
12
      ...options,
13
      token: process.env.NEXT_DATOCMS_API_TOKEN,
14
      environment: process.env.NEXT_DATOCMS_ENVIRONMENT,
15
    },
16
  ]);
17
}

This new version dedupes requests, supports all CDA header modes, and lets you control if — and for how long — you want to cache the result of the query with the revalidate option:

// cache the query result indefinitely (until next deploy)
await performRequest(query);

// cache the query result for a maximum of 60 seconds
await performRequest(query, requestInitOptions: { next: { revalidate: 60 } });